Eighteen teammates who read the whole project.
Pick a Nootie — status, planning, risk, QA, blockers, backlog and a dozen more — point it at a project, and it reads your real tasks and meeting summaries and writes you a briefing on what is slipping and what to decide next.
It never moves a task, changes a date or assigns a person. That distinction is the whole design.
Status Nootie
Engineering project · every weekday, 08:00
- Reads your tasks3 past due, 1 unowned
- Reads meeting summariesScope changed on Monday
- Writes the briefingWhat to decide first, and why
It reads only what you could open yourself. Every run it writes is kept, on the Activity tab.
Three things a Nootie does for you.
A briefing is only worth reading if it is grounded. Everything below comes from the work itself — the board you can see and the meetings you were in.
Names what is slipping
Which tasks are past due, which have nobody on them, and which decision is holding the rest up — from your live board, not from a model's impression of it.
Writes the update you owe
The standup, the status note, the risk list. Drawn from your real tasks and the summaries of the meetings you actually had.
Turns up without being asked
Run one on demand, or put it on a schedule — daily, weekdays or weekly. A schedule fires once per period even if the sweep runs more often than that.
Hire the angle you're short of.
Eighteen specialisms, assigned per project, on one page with a roster, a per-project view, their schedules and everything they have ever written.
- Some roles work from tasks alone and say something real on day one; the rest need recorded meetings or shipped work, and the page sorts them accordingly rather than hiding any of them
- One engine behind both the in-project badge and the roster page, so the same teammate cannot give two different answers
- A suggestion to hire one only fires when there is a number to point at, and it quotes that project's own number
- Every run, scheduled or manual, is written down
The half that is easy to leave out.
- It never moves a task, changes a date or assigns a person — that is Autopilot's job, on a different page.
- It reads only what you could open yourself. A private project you are not on is invisible to it.
- It can leave a comment on a task when it finds something concrete — once per point, labelled as AI, and switchable off for the whole workspace.
- Every run it writes is kept, so a briefing you disagree with can be read back and argued with.
- NorthwindRe: launch scopeAction
- Dev leadMigration is mergedFYI
- BillingInvoice #4821Later
Off until you turn it on: triage posts message bodies to a model, so the consent is checked on the server, not by hiding a button.
An inbox that knows which project this is.
Connect Gmail, Outlook or IMAP. Noots files a thread onto the right project, keeps drafts, sent and archive in step, and — if you ask it to — surfaces what needs action.
- Triage, summaries and notifications are each off by default and enforced on the server
- File any email onto a project, attaching its files as a copy
- Extraction proposes tasks; it never edits work you already have
- Schedule a send, in a timezone the picker names out loud
The status update writes itself. You still decide.
Free to start. AI mail triage and summaries need the Team plan; the teammates themselves are not tier-locked.
Works alongside Slack, GitHub, Jira and the rest of your stack
What we don't claim
- A Nootie is advisory: no task moves, no date changes, no assignment.
- Task comments are bounded to one per point and can be switched off workspace-wide.
- Nothing is read that the person running it could not open themselves.
- AI mail features are opt-in, per mailbox, and checked on the server.
