Author here. When working on optimising my workflow, I noticed that some of the now famous ‘loops’ for Codex agents were loops that burned tokens to discover nothing happened. This is true especially for some workflows such as having a Chief of Staff thread checking emails etc.WakeWire is a small local daemon that inverts this. Events (GitHub webhooks, Gmail via IMAP IDLE, Slack Socket Mode, any signed webhook like Linear, Sentry, etc.) get injected as turns into your existing Codex threads. The agent sleeps until something actually happens.We’re using Codex s app-server. Speaking to it directly (instead of scraping codex exec) gets us real busy-detection and turn-completed signals. Additionally, the daemon can host a shared app-server that codex --remote attaches to, so you can watch events wake your thread and tokens stream in live.Unfortunately this isn’t allowed in the Codex App since that runs an embedded app-server that can t attach externally, so live view is CLI-only.Would love feedback!