Cogno reads the places your team already works — Slack, meetings, Notion — and decides
what should happen next, filing each call as a suggestion with its reason attached. Accept one
and a coding agent picks it up on your computer, a teammate’s, or a team server, and delivers a
pull request. Nobody writes a prompt or opens a ticket to start it.
Start here
Get started
Sign up, install the desktop app, and watch your first task get built.
Concepts
Workspaces, projects, tasks, machines and environments — the model everything else uses.
Connect your sources
Slack, Microsoft Teams, Notion, Google Calendar. Suggestions are only as good as
the signal.
Set up a project
A project is its repository set. That is how Cogno knows where work runs and where pull
requests belong.
What Cogno can do
Files tasks from your Slack, meetings and Notion
Files tasks from your Slack, meetings and Notion
The follow-up buried in a Slack thread, the “we should fix that” from a meeting, the Notion
comment nobody turned into a task. Cogno reads your team’s activity as events, weighs them
against the tasks you already have, and files what it thinks should happen next.Each one lands as an ordinary task in the status it belongs in, carrying the mark of where
it came from — from Slack, from GitHub — so “why are we doing this?” is answered
without opening anything. See What Cogno proposes.
Watches the channels and repos you point it at
Watches the channels and repos you point it at
In a project’s settings you pick the sources it should follow — a Slack channel, a GitHub
repository — and write one sentence per source saying what Cogno should do about what turns
up there. “Anything customers report here becomes a bug in this project”, say.You write that once. It applies to everything that arrives afterwards, so there is no prompt
to compose per task and no schedule to keep. See Set up a project and
Instructions.
Joins your meetings and writes up the follow-ups
Joins your meetings and writes up the follow-ups
The Notetaker joins your calendar meetings, and the desktop app records Microsoft Teams
calls and Slack Huddles. What was decided comes back as a summary and as suggested tasks,
already pointed at the right project. See Record meetings.
Holds work that isn't due yet, and brings it back
Holds work that isn't due yet, and brings it back
Plenty of what your team says is worth acting on, just not today: the thread that only
matters once a pull request merges, the fix promised for after the release. Cogno keeps those
against the project and looks at them again later, instead of dropping them or filing them
now as noise.You do not have to be the one who remembers, and when something does come of it your
Inbox tells you.
Runs anywhere your team has a machine
Runs anywhere your team has a machine
The same task can run on your computer, on a teammate’s, or on a team server you enrol —
wherever the project’s environment lives. Nothing is pinned to one desk, work waits rather
than failing when no machine is free, and you can take any session over in your own terminal.Wherever it lands it runs through the Engine in that environment: a coding agent —
Claude Code or Codex — with your checkout, your tools and your credentials, not a
cloud sandbox holding a copy of your repository.What comes back is a branch and a pull request on GitHub, opened straight from the task. You
stay the reviewer: Cogno proposes Done when it sees a merged and deployed PR, but it
never merges for you. See Run an agent on a task, Machines and
Resume a session in your terminal.
Keeps statuses true to what is actually happening
Keeps statuses true to what is actually happening
Statuses describe reality instead of intent. In Progress only ever holds queued or running
work — it cannot be entered by dragging a card — delivered work waits in In Review, and
stalled items get swept back so the list never lies to you.See Task statuses.
Learn more
Start with the model, then the guide for whatever you’re doing:- Concepts — the loop in depth: events, suggestions, agents, machines and environments.
- Work with tasks — triage, create work, talk to the agent, review what it delivers.
- Memory and Instructions — what Cogno knows about your team, and the standing rules it follows. Both are plain text you can edit anytime.
- Machines — the Engine, environments, and enrolled servers.
- Inbox — how finished work finds you.
- Troubleshooting — when something doesn’t behave.