Spreadsheets that know
who changed them, and why.
Candidates, customers and vendors in typed tables, edited by people as a grid and by agents in SQL. When an agent changes a row it names the message it acted on, and anyone can take the change back.
Sheets
What it does
A grid that feels familiar
Keyboard first, with paste from your spreadsheets, a fill handle, views as tabs, find, and a record panel for one row at a time.
Typed columns
A column holds one kind of value: a date, a person, an option from a list, a file. A value that does not fit is refused, whoever sends it.
SQL for agents
An agent asks a sheet in SQL instead of reading it, so a question about a sheet of any size costs a few lines of its context.
Changes with their reasons
After the debrief in #hiring, Scout moves the candidate to Onsite and cites the message it acted on. The row's history shows who changed it and for whom.
Rules the rows keep
A sheet knows its stages, what each column means and the moves its workflow allows, and a write that breaks them is refused with what is allowed.
Undo for every write
Each write is one change that can be reverted. An agent marks a value it is unsure of, and a review shows what agents changed since you last looked.
For agents
How an agent
works here
Agents use the same API as the apps, through the together CLI or its MCP tools. These are the commands an agent runs on this part of the workspace.
together sheets show candidatesIts columns, what each means, its rules and stagestogether sheets sql "SELECT stage, count(*) FROM candidates GROUP BY stage"Counts the candidates at each stagetogether sheets set candidates r-41 stage=Onsite --source msg:m-214Moves a row, citing the debrief messagetogether sheets changes candidates --row r-41Who changed the row, and for whom
What changes
What it changes
for your team and its agents
Rows that move after the meeting
The debrief ends and the pipeline is already up to date, with each move citing what was said and by whom.
Answers without an export
Mara asks how many candidates sit at each stage and gets the count from the sheet itself, with the query that produced it.
Safe to hand to an agent
Strict types and a dry run catch a bad write before it lands, and any change can be taken back, so letting an agent write to the sheet is a small decision.
Related
It works
with the rest of Together
