Your own types
Fields, states, owners, dates and files. Every record is a card in the chat and a row in a list you can sort, filter and search.
Records & automations
Records that work on themselves
Your own record types (tasks, deals, tickets, releases, invoices), linked to each other, with triggers that hand the next step to an AI agent. A database and an automation tool in one, where the automation does the actual work.
Linked to each other
A release lists its epics, an invoice points to its project. Links show on both sides and work across channels.
A thread per record
Discuss a ticket without flooding the channel. The agent works in that thread too, next to the files and the history.
Triggers hand the next step to the agent
A rule on a record type starts an agent run in that record's thread. Everyone sees what the automation did and can step in.
- When a record is created: a new ticket gets triaged and a draft reply
- When a field changes to a value: a project marked done gets its final invoice drafted
- When any field changes: a new owner gets a briefing
- Buttons on cards: one tap sets a state, and the app shows that the agent is on it
No setup screens. Just say what you track.
Every space has an owner-only setup chat. Describe your records and rules in plain words; the agent creates the types, fields, states and triggers. Change them the same way later.
Start from a kit
A kit sets up channels, record types and rules in one tap. Everything it creates can be changed afterwards.
ITSmall IT team
Services, releases, epics, runbooks and postmortems, linked together. A shipped release gets its changelog written; a published postmortem turns its action items into tasks.
$Agency or studio
Clients, projects and invoices. A finished project gets its final invoice drafted; an overdue invoice gets a polite payment reminder.
?Support desk
Tickets with priorities and tags. Every new ticket is triaged with a draft reply; a ticket waiting on the customer gets a follow-up.
Your tracker's issues are records too
Connect a Linear team or project to a channel: its issues arrive as records, sync both ways, and the same triggers and buttons work on them. Jira and Trello are next.
Automation you can trust
Always visible
Every run is announced in the record's thread and in Activity.
No loops
The agent's own edits never fire rules again.
One at a time
One run per record and rule; at most 30 runs an hour per space.
Who sees what
Each record type has its audience, and a record can be locked.
Free on your own machine
Records and automations come with every space. Install the service, create a space, pick a kit.