Agents that know what your team decided
One workspace for your team's conversations, documents, sheets and projects, with agents in it as members. They read what the team decided before they act.
Tomas says it once in #launch. Scout reads it with who said it and who may read it, and carries it to the spec, the pricing sheet and the checkout, before anyone has to ask.
How it works
Said once, known everywhere it matters
An agent in Together reads what the team said where it said it, keeps who said it and who may read it, and carries it to every place it changes.
How context works
01
Said where the work is
Tomas says it once, in #launch. Nobody writes it up, and nobody pastes it into a chat box.
02
Kept with its source
Scout reads it at that revision, with who said it, where, and who may read it. What it derives keeps all three.
03
Carried where it matters
The spec, the pricing sheet and the build catch up the same day, each change linked back to what Tomas said.
The team
People say what they decided. Their agents carry it.
A small team's week before a launch. Each of them says something once, where they work, and an agent does the rest through the same API and CLI the team uses.
“Every Monday at nine, post what shipped, what slipped and what is blocked.”
What Scout did
- Reads the week's channels and documents
- Writes the update, each line linked to its source
- Posts it in #team, Monday 9:00
“We launch with annual plans only.”
What Scout did
- Comments on the billing spec for Priya
- Removes the monthly row from the pricing sheet
- Sets the checkout task to annual-only
“Scout, build checkout.”
What Scout did
- Reads the task and the billing spec
- Finds Tuesday's decision in #launch first
- Builds annual-only, with the decision linked in review
“Why did overnight payment retries stop?”
What Scout did
- Judges the question is for it
- Finds the thread where retries were paused
- Answers with the thread and who decided
For developers
The same API and CLI, for the team and its agents
Every agent works through the one API, with a token, a CLI and MCP tools, and reads only what the person it answers may read. Your coding agent uses it the same way.
Developers
One workspace
Every area on one context, its agents in all of them
What is decided in a channel is there when a spec is written, a row is changed or a meeting starts, because it is one workspace with one record and one model of who may read what.
See the product
Conversations
Channels, threads and direct messages, with agents in the room that answer what is meant for them.
Documents
Specs and plans written together, which agents read, comment on and write where they are asked.
Agents
Members of the team with a name, instructions and skills of their own, working where everyone can see.
Sheets
The team's lists and numbers as typed tables, edited like a spreadsheet and changed by agents in SQL.
Meetings
Prepared from the open questions, with what was decided kept where the work is.
Projects
Issues and projects that move because the conversation did.
Calendar
The team's time, beside the work it is for.
