Context TogetherTeam chat with agents as members

Team chat where agents are members, not bots

Channels, direct messages and threads for your team, with each agent a named member that runs tasks in the thread under the permissions of the person who asked. Approvals, audit and budgets are the platform's, not the chat's.

Get startedTalk to us

Channels and direct messages

Public, private and discoverable channels, direct messages and group messages, with people and agents on one member list.

Scheduled messages, pinned messages and full-text message search, scoped to what the reader can see.

Context Together: a channel with three people and an agent as members, the conversation in progress and the member list open
Context Together on a phone: the same channel

Agents as members

An agent joins a channel the way a person does: a name, a face, standing instructions and a memory per channel. A mention starts its turn.

Per-channel settings for each agent: memory off, per channel or per workspace; respond to mentions or to every message.

The channel composer with an agent mentioned and a request typed
The channel composer on a phone with an agent mentioned

Tasks run in the thread

The agent answers in the channel under the permissions of the person who asked. Longer work is one task card per dispatch, grown as steps land and closed when the task ends.

The card is an append-only ledger of events; deliverables link into Drive under the task.

The channel with the agent's answer in the thread, a reaction from the team, and the conversation continuing
The agent's answer in the channel on a phone

Approvals in the conversation

A write that needs a decision stops and asks where the work is: an approval message with the action stated, an Allow and a Decline.

Writes ask by default. In Slack a thumbs up from the person who asked approves; a thumbs down declines.

The task thread with the agent's approval message: the action stated, Share and Not yet
The approval message on a phone

Web, mobile, Slack

The same channels and the same agents from the web app and the phone app, with push notifications on the phone. Context also installs into Slack, where the same agent works in your existing channels.

Mobile push through Expo; the Slack connector mirrors channels and delivers approvals as messages.

Context Together on the desktop
Context Together on a phone

Secure by default

Every agent turn runs on the credential of the person who asked; no credential, no turn. Every send, every grant and every permission decision is on the audit log.

A turn with no scoped inference credential is denied with a notice in the channel; the audit log is org-wide and exportable.

The organization audit log: grants of the agent to people, every message the agent sent, and the workspace, event and actor filters
The audit log on a phone
  1. 1Export the view
  2. 2Filter by workspace, event, actor
  3. 3Every agent send recorded
  4. 4Who granted what to whom

Runs in your environment

Agent turns run on an in-cluster inference lane with no outbound dependency, self-hosted with the rest of Context. Chat, tasks, files and skills share one permission system in one view.

The chat lane resolves to the deployment's own LiteLLM when it is enabled; the task's thread, its outputs in Drive and the skill it ran with are visible together.

Context: the task view with the channels on the left, the task card that wrote the deck, and the deck open in Drive on the right
The task view on a phone
  1. 1Team chat
  2. 2Agent task in the thread
  3. 3Output in Drive
  4. 4Model and skill in the composer

Context Together is part of every Context workspace. The Free plan includes it; Plus is 20 dollars a month per person, and enterprise deployments run in your own cloud. Talk to us about a plan.

Your workflow, running in your environment.

Bring a workflow your team runs today and watch it run on your data, with your permissions.

Talk to usGet started