Nonstall reads Slack, your repositories, your tracker and your docs — then tells you what needs you, what is stuck, and who is waiting on whom. The text never leaves your machine.
Alex is waiting on your call on the pricing capslack · #product · 2h · you were asked directlyNeeds you
PR #482 has been waiting for your reviewgithub · web-app · 26h · blocks 2 peopleStale
Agreed in chat on Tuesday, never made it to the boardtracker · suggestion from #engNeeds you
The pricing spec changed after the decision was madenotion · pricing v3 · edited 5h agoFYI
You took: send the migration plan by Fridayweekly sync · today, 11:04Yours
Reads the tools you already pay for
01 — One place
Everything lands where it belongs.
Connect the tools you already use. Nothing to tag, no per-project setup — the first minute of indexing already gives you a real working day, ranked by what actually needs you.
Slack — threads and mentions, including the ones that went quiet on you
Git — pull requests and reviews, and who is blocked behind them
Tracker — tasks, including the ones only ever agreed in chat
Docs — decisions and specs, and when they quietly changed
Meetings — what was decided and who walked away with it
Not a promise on a policy page — an architecture. Your messages, your code and your documents are indexed into a database on your own disk. There is no upload step, because there is nowhere for it to go.
Everything local — the index lives on your machine and never leaves it
No account, no cloud — nothing to sign up for, nothing to breach
Your AI subscription — we never touch, store or proxy a vendor token
Agents post nothing — no model has a write path to your Slack
The same index that saves an engineer an hour of scrolling is what lets whoever runs the company see it end to end — and catch a problem while it is still small enough to fix in a message.
For the team — what needs you, ranked, with the reason in plain words
For the team — the end-of-day report writes itself from real work
For the admin — who waits on whom, across teams and tools
For the admin — a live map of the company, not a monthly deck
04 — Integrations
Add as many as you need. Hundreds, if that is what you run.
You do not hunt for a settings page. You say what you want connected in the chat, and the connector appears right there — with a button, a scope list and a test that runs in the same thread.
Known tools — one click, granular scopes, revocable
Anything else — any MCP server: paste a URL and a secret
Write-tools — off until you turn them on, one by one
No. Messages, code and documents are indexed into a local database and stay on the machine. The server holds references and counters — thread ids, states, seat and plan — so a team can share structure without sharing text.
Which AI does it use, and who pays for it?
Yours. The app drives the Claude or Codex CLI you already run on a subscription, or takes an API key. There is no markup on tokens because the tokens are never ours.
Will it post in Slack pretending to be me?
Never. No model has a write path. A deterministic poster sends only message types on an explicit whitelist — nudges and reports you approved — and every line it sent is readable in the app.
What can my admin see about me?
Structure, not content: what is blocked, how long it has been waiting, which dependency crosses which team. Not your messages, not your DMs — the app cannot show what it never uploaded.
Does it keep working when my laptop is closed?
The desktop app indexes while it is open. For round-the-clock work — night reports, nudges, incident watching — you run a small node: a container on your own hardware, or ours if you would rather not.
My tool is not in your list.
Then it plugs in through MCP. Paste the server URL and a secret in the chat and it becomes a source like any other. Read-only until you decide otherwise.
Nothing waitson somebody noticing.
Install it, connect Slack, and watch your first real working day get computed in under a minute.