Your issue tracker, with your workflow, readable by every agent.
Projects, tasks, cycles and comments as entities, with statuses that change only through your actions. Agents create, assign and close tasks with the person's permissions, and tasks link to deals, clients and contracts in the same workspace.
Board
One cycle's board. Each task carries its labels, its assignee and the client or deal it belongs to.
Product, engineering and delivery teams
Tell your agent how work moves in your team. It writes the entities, the status actions and the roles, and every agent you use can work in it.
- Projects, tasks, cycles and comments as entities, with statuses that change only through your actions.
- Closing a task needs a resolution, because the action says so.
- Agents create, assign and close tasks with the person's permissions.
- Tasks link to deals, clients and contracts in the same workspace.
What it covers
Tasks with your workflow
Projects, tasks, cycles, comments and labels, with statuses that change only through your actions.
Linked to the rest of the company
Tasks link to deals, clients and contracts in the same workspace.
Agents as teammates
Agents create, assign and close tasks over MCP with the person's permissions.
GitHub
Pull requests and issues load through an API-key connection with a fine-grained token, and link to the tasks they close.
Built from typed blocks
No new product to buy: the blocks below, written by an agent into your workspace's repository and deployed with one command.
None required.
$ segmentstream deploy
Every block ships together from one git repository your company owns. SegmentStream runs it.
- name
- lead
- status
- task
- cycle
- title
- status
- due
- resolution
- project
- assignee
- deal
- assign
- moveStatus
- close
- starts
- ends
- project
- task
- body
- task
- author
- name
- colour
- task
The rule is code, not a setting someone can skip.
Every change goes through an action. The role that may run it is checked first, then the rule inside it. The same check applies to people in the app, to API keys and to agents over MCP.
export const Task = entity("task", {
description: "A piece of work. Closing it needs a resolution.",
properties: {
title: p.text(),
status: p.select(TASK_STATUS, { default: "todo", managed: true }),
resolution: p.select(RESOLUTIONS, { optional: true, managed: true }),
},
relationships: {
project: rel.one("project", { inverse: "tasks" }),
assignee: rel.one(User, { optional: true, inverse: "tasks" }),
deal: rel.one("deal", { optional: true, inverse: "tasks" }),
},
}).actions((self) => ({
close: action({
description: "Close a task with a resolution: done, won't do or duplicate.",
input: Schema.Struct({ task: self.ref, resolution: Resolution }),
handler: ({ input }) =>
Effect.gen(function* () {
const task = yield* self.get(input.task, { forUpdate: true });
yield* self.update(task, { status: "closed", resolution: input.resolution });
}),
}),
}));- Linear
- Jira
- Asana
- Trello
- Notion databases
Our engineers model your workflow with your team, import your projects and open tasks, and link them to the clients and deals they belong to.
Enterprise, with our engineers
Our engineers model your workflow with your team, import your projects and open tasks, and link them to the clients and deals they belong to.
Self-serve, with your own agent
Tell your agent how work moves in your team. It writes the entities, the status actions and the roles, and every agent you use can work in it.
Related solutions
Questions
Does it connect to GitHub?
Through an API-key connection with a fine-grained token, held by the platform. Pull requests and issues load on a schedule and link to the tasks they belong to.
Can agents work in it?
Yes. Agents create, assign and close tasks over MCP with the permissions of the person they act for, and the company agent can take "add a task for…" in Telegram.
How do we move from our current tracker?
Projects, open tasks and their history load once through the ontology API, from Linear, Jira, Asana or Notion through their APIs. Both run side by side until the team switches.
Rather have it built for you? Start a pilot.
Our engineers model your workflow with your team, import your projects and open tasks, and link them to the clients and deals they belong to.
- One solution, on your data, in your own workspace
- First version live in two weeks
- Parity proven before anything is switched off
- Fixed scope and price, credited to your contract if you continue
Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.
How the pilot worksYour company’s software, built by agents, owned by you.
$ segmentstream workspace create acme --region eu --subdomain acme
▸ Created workspace acme · database, warehouse and a private git repository
$ segmentstream workspace WORKSPACE-ID clone acme && cd acme
▸ your agent writes the five folders and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, ontology API and MCP tools live for your invited members
Our engineers build the first version on your data in two weeks, at a fixed price.
Or join the waitlist for self-serve:
Self-serve opens to the waitlist first.