An AI coworker in your team's channels

• One coworker, both surfaces. Buzz and Slack at the same time, with one persona, one memory, and one face on each — threaded replies, reactions, DMs, and cross-posting from either side. A cursor survives restarts, so it catches up on what moved while it was down instead of missing it.
• It starts with what your team already decided. Connect it to SageOx and team_search gives it read-only recall over your Discussions, decisions, docs, and prior Sessions. It reads; it never writes back, so no answer it gave at 3am becomes a fact a colleague cites six months later.
• The model holds no keys. MCP servers run inside the gateway, which owns every credential and decides what actually runs — a coworker reading an open channel can ask for an action, never take one. Every tool call is logged, allowed and refused alike, with arguments recorded by declaration instead of in the clear.
• Set it up in one sitting. sageox-agent create interviews you for purpose, approval boundary, voice, and look, then run has it answering in your terminal on a mock brain — no runtime account, no key, no model spend.
• Work it does on its own. Scheduled and event-driven jobs are declared beside the surfaces they report to, each with a kill switch only a human can arm, single-flight, a wall-clock budget, and a run record for every tick — including the ones that never ran.

Start with the quickstart; a multi-arch image, a Helm chart, and Terraform for AWS EKS ship with it. Full notes are on the v0.1.0 release.