[lydakis]

Requested by George · project thread

Opens Sonny's lookout to external services: you write a poller (for example for Slack), and the lookout passes what it prints to the agents that subscribed. The daemon and the agent CLI don't change.

What it does

• You set a source up in ~/.agent/config.toml:

  [sonny.sources.slack]
  command = "~/bin/slack-poll --channel eng"
  every = "1m"   # how long after it exits it runs again; a minute unset

  The lookout runs it with sh -c, in its own process group, with SONNY_SOURCE and SONNY_SOURCE_DIR (STORE.sources/NAME, where the poller can keep its cursor). Each printed line is one event. It can be plain text, or JSON with text and optionally id, from, url and urgent. A poller that exits runs again after every, and a stream that never exits works too. An id seen lately counts as news only once. The settings are re-read every 15 s, and a stopping lookout stops its commands.
• Agents only subscribe, through a new sources: [...] field on a subscription. An unknown name is refused, and the tool result lists the sources that exist. Agents can never define a command, so a sandboxed bot can't use the lookout to run one.
• No judge reads sources, which matches the judge-free lookout direction. Every event is told. An event the poller marks "urgent": true steers a busy subscriber, and the rest wait until it rests. look_for alongside sources is refused. Events still waiting follow subscription changes: a source no longer subscribed to is dropped.
• Delivery: a separate note starting From your sources: that quotes each event's text as a JSON string. It goes out with origin lookout.sources, so the approver never reads Slack text as George's words. Its request id is lookout-*, so it stays quiet in Sonny and shows folded as ↳ From your sources · slack 2. /background lists the subscription as source slack · every event.

Code: sonny/src/lookout/sources.rs (new runner and note), additive hooks in lookout/mod.rs, plus subs.rs, served.rs, transcript.rs and client/src/config.rs (beside [sonny.mcp_servers]). Docs: a new "Sources" section in docs/LOOKOUT.md and a row in sonny/README.md.

Also carries a one-line fix for main's build: trigger::restamp (#318) still called Places::plist, which #344 renamed to job.

Codex's security note on outside text reaching a tool-enabled turn is logged as #348.

Screenshots

Captured from a live run: a real daemon, Sonny and lookout, a scripted model, and a poller printing a lunch message plus an urgent failed deploy.

Tests

• New unit tests: config parsing, every, line parsing, id dedupe, the runner running a real command twice with its state folder, the note, subscription matching and re-matching, and wake_sources against a stand-in daemon (origin, queue vs steer, byte budget).
• New live test test_what_a_source_prints_reaches_who_subscribed_to_it. After rebasing on main, AGENT_TEST_RUNTIME=1 python3 -m unittest tests.test_lookout tests.test_served passes, 20 tests.
• cargo test -p sonny -p agent-client passes.

Follow-ups not done: showing each source's last run in /background, and keeping seen ids across lookout restarts.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_013jkdGCueMjCVQsvkY7iTCR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T04:59:08.277766Z	22e7e90	New commits
🔒 Security Review	✅ Completed 2026-10-29T05:04:09.378234Z	22e7e90	New commits

Security findings

Advisory findings (1)

• 🟡 Isolate source events from tool-enabled turns · High

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a18799ecdc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d4c6a8ceb2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

🛡️ Codex Security Review · Automatically triggered

Here are some automated security review suggestions for this pull request.

Reviewed commit: a9457efacb

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.