Stop writing status updates.
Keel reads your team's chat, meetings, and commits, keeps the plan true, and tells you what is slipping and why. Every change to the plan arrives as a proposal you approve.
Signals reaching Keel, sample project
One message in chat. Four days gone from the launch.
of slack before launchScroll to watch Keel follow the delay through every task that depends on it.
Shift 3 tasks +4 days
Auth service moved 4 days. Payments API, App integration, and Mobile release depend on it. Launch keeps its date but loses all of its slack.
Backend auth is delayed 4 days.
- BackendAuth serviceNov 3Nov 3
- BackendPayments APINov 7Nov 7
- WebApp integrationNov 12Nov 12
- MobileMobile releaseNov 14Nov 14
- MilestoneLaunch4d slack4d slack
One loop runs the whole plan
Whatever comes in, a chat message, a commit, a meeting, it travels the same path. Only your approval changes the plan.
- Signal
Someone writes, pushes, or says something that affects the plan.
- Risk
Keel links it to a task and works out every task downstream.
- Proposal
The change is written up with its reasoning and the source attached.
- Your approval
Approve, edit, or reject. Nothing moves before this step.
- Record
The change is logged with who proposed it and who approved it.
Start where the work already is
No new habits. Keel picks up the briefs, meetings, and questions your team already has.
Paste a brief, get a plan you can check
Keel turns a rough brief into tasks, estimates, and dependencies. It flags what it could not work out instead of guessing.
- Loops in the dependencies are caught before anything is created
- Tasks with no clear owner are marked for you to assign
- Nothing is created until you approve the plan
we need stripe checkout live before the nov 18 launch. backend owns auth + payments api, web does the app integration, mobile ships after that. design needs new pricing screens. not sure who does the receipts email??
- Checkout
- Auth service5dBackend
- Payments API4dBackend, after Auth service
- App integration3dWeb, after Payments API
- Mobile release2dMobile, after App integration
- Pricing
- Pricing screens3dDesign
- Receipts email2dNo owner yet. Pick one before approving.
Meetings end with the notes already taken
Upload the recording or the transcript. Keel pulls out decisions and action items, with owners and dates, and links each one to the moment it was said.
- Decisions go to a searchable decision log
- Action items arrive as proposals, not surprise tickets
- Every item links back to the part of the meeting it came from
- Maya Let's drop Apple Pay from the first release.
- Priya Fine by me, it was the riskiest part anyway.
- Dev I can have webhook retries done by Thursday.
- Priya I'll write the migration note for support.
- Decision
Apple Pay moves out of the first releaseSaid at 14:02 by Maya - Proposed task
Webhook retries, Dev, due Thu Oct 30Said at 14:05 - Proposed task
Support migration note, PriyaSaid at 14:09
Ask about the project, get an answer with sources
Press Ctrl K and ask in plain words. Every sentence in the answer points to the message, commit, or meeting it came from.
- Answers only use what you already have access to
- When there is no evidence, Keel says so instead of guessing
Auth service. Dev said it is delayed 4 days1, and no commits have landed on the auth branch since Monday2. That uses all 4 days of slack before the Nov 18 launch3.
- 1Message in #launch from Dev, Oct 22
- 2GitHub, auth-refresh branch, last commit Oct 20
- 3Critical path for Northwind checkout launch
You decide how far the agent goes
Pick one setting for the whole workspace. New workspaces start with every change waiting for a person, and you can loosen it when you trust it.
Even small changes wait for a person. This is where new workspaces start.
- Add a comment ◆ Waits for approval
- Add a label ◆ Waits for approval
- Link a commit to a task ◆ Waits for approval
- Shift task dates ◆ Waits for approval
- Reassign a task ◆ Waits for approval
Every warning shows where it came from
A task marked at risk tells you why in one line, then shows the messages and commits behind it. Dates come from dependency math, not from the AI, so the same plan always gives the same answer.
Moved 4 days because Payments API moved, which waits on Auth service.
- Message in #launch, Oct 22Dev: “Backend auth is delayed 4 days.”
- Commit on auth-refresh, Oct 20a41c9e2 fix token refresh on expired sessions
Let the plan keep itself.
Connect GitHub, invite your team, and see your first risk the next time someone mentions a delay.