An always-on, event-driven agent that lives on your machine.

sedge is a coding agent with a daemon behind it that keeps working after you close the terminal.

$ curl -fsSL sedge.sh | sh

or npm i -g @sedge-hq/sedge

  • It keeps going. A daemon wakes for each event (a message, a timer, a webhook, a sensor, your CI failing), does the work, and sleeps again. A run a restart cuts short picks up where it stopped.
  • It reaches you. Write to it on Telegram or Slack. It answers there, and asks before anything risky with Approve and Deny buttons.
  • It stays quiet. Conditions, throttles and a cheap triage model drop the events that need nothing, so you hear about what matters.
  • It stays within bounds. Optional limits on runs and spend, and an OS sandbox that keeps its commands away from your credentials.
  • It remembers. A small memory it keeps itself, checked against what happened every night.
  • It's a coding agent. The TUI is pi, with its models, commands, MCP servers and skills. The daemon gets your MCP servers and skills too.
How sedge works: channels, signals, timers, the terminal and other agents put events into the inbox, which drops repeats, batches, triages and keeps to your limits; durable runs, many at once, work with memory, skills, MCP servers, tools (optionally sandboxed), approvals and subagents; what they send leaves through the outbox to you, and your reply comes back as an event.