SageOx

The Slack integration, authorized per team, publishes into the channels a team picks (discussion murals, live join links, team murals and welcome notes), SageOx listens in Zoom and Google Meet calls it is invited to, connects to GitHub or GitLab with the access granted at setup, and its open-source AI coworker answers in the Slack thread that asked and can wake a named person. Those are native, authorized write actions in real systems; Slack listening is marked not yet available.

SourceSageOx, sageox.ai/docs integrations, integrations/slack and your-data, and sageox.ai changelogread 2026-09-21

Agents that other tools launch and orchestrate (OpenClaw, Factory Droid or custom orchestration) are where SageOx works, and its own surfaces prime, capture and plan; no workflows that sequence, branch or retry steps, or combine deterministic nodes with agent steps, are documented.

SourceSageOx, sageox.ai/docs agent-factories, how-it-works and plansread 2026-09-21

Team documents added to Team Context are indexed automatically, so repo-based AI coworkers see a catalog at session start and read full content on demand, and MCP clients search and retrieve the same knowledge; ox query runs semantic search across Team Context, CodeDB builds a local semantic index of the codebase and its git history for coworkers to query, and plan badges cite the real artifact behind each claim. That is a maintained, refreshed structure over the customer's knowledge that cites its sources.

SourceSageOx, sageox.ai/docs team-context, codedb, cli/query and plansread 2026-09-21

An AI coworker authors a visual plan that a person reviews and decides go or no-go on, and the coworker revises the same page on feedback before the work becomes a pull request. That is a shipped review surface for the agent's intended work; no approval step that holds the agent until someone signs off, and no autonomy modes for low versus high risk actions, are documented.

SourceSageOx, sageox.ai/docs plansread 2026-09-21

Access control is documented: team invitations with owner, admin or member roles, MCP connections as scoped OAuth grants that see only the teams and repos the user belongs to and are listed and revocable in security settings, personal access tokens named in audit logs and revocable immediately, AES-256 encryption at rest, and redaction before observations are stored. No certification or audit report is published.

SourceSageOx, sageox.ai/docs mcp, cli/pats, cli/team, discussions and your-dataread 2026-09-21

When a coding agent's session ends, ox commits it to the repository's Ledger and summarizes it: the questions, the reasoning, the decisions and the code that came out of it, viewable session by session with ox session view, with each merged pull request linking the session and plan that produced it; the Agent Toolkit also records stranded tool calls, and personal access tokens appear by name in audit logs. That is a run level record of what the agent did, with audit logs beside it.

SourceSageOx, sageox.ai/docs session-recording, plans and cli/pats, and sageox.ai changelogread 2026-09-21

Team Context keeps a memory directory of team memory organized in time-based layers, built automatically from recorded discussions and observations, with an auto-generated MEMORY.md index that repo-based AI coworkers load at session start; it is team-wide, held in a git repository the team can browse, edit, commit to and diff, and built-in redaction runs before observations are stored, with team-set redaction rules. So the memory has a clear scope and a time based lifetime, and the team can review, edit and delete it.

SourceSageOx, sageox.ai/docs team-context and your-dataread 2026-09-21

Team Context, Ledgers and recordings live on SageOx's hosted git server in us-west-2 with a local checkout synced to each machine, the CodeDB index stays on the customer's machine, and the open-source AI coworker is the customer's to run. The hosted data sits in one stated region, with no choice of region or self hosted option for the SageOx service.

SourceSageOx, sageox.ai/docs your-data and sageox.ai changelogread 2026-09-21

One ready to run AI coworker for Buzz and Slack, which starts from the team's memory, comes in SageOx's open source Agent Toolkit, and ox coworker lets a team add, list and load expert coworkers written as markdown files in a documented format. The coworker definitions are the team's own; no library of ready made agents or templates to choose from is documented.

SourceSageOx, sageox.ai/docs cli/coworker and sageox.ai blog and changelogread 2026-09-21

Scheduled jobs run SageOx's AI coworker, including jobs whose body is a prompt so the coworker does light scheduled work on its own, and it answers mentions and missed DMs in Slack; in repositories, agent lifecycle hooks start session capture automatically, and the docs give a scheduled workflow for daily distillation and queries in CI.

SourceSageOx, sageox.ai changelog and sageox.ai/docs cli/ephemeral-mode and claude-coderead 2026-09-21

Each AI coworker file can set its model tier (opus, sonnet or haiku), a coworker's model can be overridden when it is loaded, the team can pick Codex or Claude as the brain behind a coworker, and repo-based coworker sessions run through the customer's own AI provider account across Claude Code, Codex, Gemini and other supported agents. The customer controls the model choice.

SourceSageOx, sageox.ai/docs cli/coworker, your-data and coding-agents, and sageox.ai changelogread 2026-09-21

A REST API with an OpenAPI description sits in SageOx's agent catalog beside an OAuth 2.0 protected MCP server whose tools search and read team knowledge and save sessions, agents can register through dynamic client registration, the ox CLI runs headless with personal access tokens for CI, cron and cloud agents, and developers can build a custom adapter to bring a new agent in. Together that is a documented API, an MCP server with write actions, and a fit into CI.

SourceSageOx, sageox.ai/.well-known/ard.json and sageox.ai/docs mcp, mcp/manual, cli/pats and developers/custom-adapterread 2026-09-21

Testing of agents against fixtures or datasets, scoring of output quality and a configurable quality gate are all absent; the documentation covers capture, Team Context, priming, session recording, plans and integrations.

SourceSageOx, sageox.ai/docsread 2026-09-21

SageOx captures discussions through browser and desktop recorders, Ox Dot and imported audio or video, and no browser, desktop or computer control by an agent is documented.

SourceSageOx, sageox.ai/docs context-captureread 2026-09-21