Chat
Talk to your agents. Hand off the work.
Ask for something the way you would ask a colleague. The agent goes to your tools, does the task on its own computer, and comes back with the result — and with the files it made along the way.
Here's the churn CSV from the board deck. Cross-check it against our warehouse, find the accounts we mislabeled, and open Attio records for the ones still active.
- workspace·read churn-q3.csv · 214 rows
- postgres·query subscriptions by account_id
- code·reconcile and diff · 11 mismatches
- attio·update 7 records · status=active
11 mislabeled accounts found
- 7 still active — Attio records corrected
- 4 genuinely churned — confirmed against last invoice
- reconciliation.csv saved to the workspace
Context
Give it the context once.
An agent does better work when it knows where to look. Point it at the channels, repos, databases, and files that matter.
Pin the resources it should know
Attach a Slack channel, a GitHub repository, or a database connection to the conversation as a scoped resource. The agent treats it as standing context for everything you ask next.
Upload the files it needs
Drop a CSV, a contract, or a screenshot into the chat. The file lands in the agent's workspace, where it can open it, transform it, and hand something back.
Everything the runtime gives it
Chat runs on the same agent as Workflows: an isolated cloud sandbox, code execution, the full APIs of your integrations, your databases, and memory of what you have taught it.
Pinned repositories
Scoped to exactly what you name.
Pinning a repository narrows an agent to the codebase you want it working on.
Pin a GitHub repository and the agent carries it as standing context — it works in that codebase without rediscovering it each time. The pin carries the integration it belongs to, so the credentials come along and stay server-side. Everything else the agent reaches — channels, databases, documents — comes through your connected integrations on demand.
What did people complain about in #support this week that we haven't filed an issue for?
- slack·read #support · last 7 days
- github·search issues in helios/api
- code·match complaints to open issues
3 unfiled complaints
- CSV export timeout · mentioned 6 times
- SAML login redirect loop · 2 enterprise accounts
- Draft issue bodies ready to file
Collaboration
One conversation, the whole team.
A chat that solved a problem is worth keeping — and worth passing on.
Fork a conversation
Branch from any chat to try a different approach, keeping the original thread and everything it already worked out.
Share a public link
Publish a conversation up to a chosen message and send the link to anyone. The rest of the thread stays private.
Share with your team
Keep a chat restricted to the people you name, or open it to everyone in your organization. Roles decide who can read it and who can drive it.
From chat to standing task
When you want it every week, save it.
A chat that keeps earning its keep becomes a workflow. Same agent, same tools, same memory — now on a trigger.
Do this every Monday and post the unfiled complaints to #product.
- slack·read #support · last 7 days
- github·search issues in helios/api
- slack·post #product
Workflow created from this chat
- Runs every Monday · full run history kept
Keep going
Where teams take it next
Workflows
Put an agent on the task
Turn the conversation into a standing task on a schedule, a webhook, or an integration event.
Integration
Slack
Read channels, follow threads, post answers — with the full Slack API behind it.
Use case
Support triage
See a full run: read the queue, group the themes, route what needs a human.
Ask an agent for something.
Start free, open a chat, and hand it the first task. Bring your team when it earns its place.