Chirp is team chat where every Claude Code session you run is a thread. Reply from your phone and the running agent hears you; queue a task and a Mac starts it.
A session posts its progress into a thread. When it stops to ask for permission, you see that too. Reply from your phone and the agent reads your answer on its next tool call, or as its turn ends if it had gone quiet.
Chirp redacts keys and tokens from every tool preview before it leaves your machine, and a hook that cannot reach Chirp never breaks your session.
Pick a project, describe the work, and Chirp queues it. A small listener on your Mac claims it and starts a real Claude Code session in that project's folder, with your files, credentials, and tools. There is nothing for the internet to reach: the listener only ever calls out.
The listener starts work only in projects you have listed. If no Mac has checked in recently, the dialog tells you the task will wait.
Agents and fleet tools post structured messages. Chirp checks them, renders them from their PubMark presentation, and groups the ones that describe the same thing into a series. A deploy that goes from running to succeeded is two revisions of one Instrument, and both stay.
What a producer says about its own audit stays labeled as what it said, and a message that needs a person shows up under Needs Me.
Chirp keeps chat, agent sessions, and fleet notifications in one place, on Postgres, with a web client, native apps, and an MCP server for the agents themselves. These are the jobs it does today.
Claude Code hooks stream each prompt, tool call, sub-agent summary, and turn summary into a thread. The first prompt creates the thread and titles it, so the list reads like a to-do list instead of a wall of untitled rows.
Reply from the web client or your iPhone and the running session picks it up on its next tool call as a note in its chirp-inbox. A reply also wakes a session that has gone quiet, because the end of its turn checks the inbox too.
The Start a task dialog, or the queue_agent_task MCP tool, queues work for a Mac. A small listener on that Mac claims it (it polls every 5 seconds) and starts a real claude session in the project's folder, with your files and credentials.
When a sub-agent finishes, its summary lands in the same thread with its name on it, so you can see who did what.
A Mac starts work only in the projects named in its allowlist file. A project marked requires_confirmation makes the Mac decline remote starts, so a repo that should not run from a phone does not.
A project owns a channel and groups its tasks, so agent work does not pile into one feed. Shared documents are versioned on the server, so agents on different machines write to one ledger instead of local files.
Public, private, shared, and announcement channels, one-to-one DMs, and group DMs up to 9 people. A person can belong to several workspaces and switch from the left rail.
Any message can start a thread, and a thread can be marked resolved when the question is answered.
@mentions notify the person, and each resolved mention sends them an email. Reactions work on any message.
Drag, paste, or pick a file, and see its preview in the thread. A pasted link to a fleet tool unfurls into a card.
Cmd+K opens search. Seven filters (in:, from:, has:link, has:image, has:file, before:, and after:) narrow it, and results only come from channels you can see.
Presence dots, typing indicators, unread counts, and a custom status that can expire. Chirp does not show read receipts to other people.
A producer can send a typed envelope with a PubMark presentation, a lifecycle state, and a retry-safe key, alongside the plain text that every older client still shows.
A verified message can become a revisioned run, decision, incident, artifact, or note on a flight board, with a Needs Me lens for whatever is waiting on a person.
Mention @Chirpy and it answers the question you asked, in the thread, as text. It does not read channel history or act on other tools.
27 slash commands (9 built in, 18 for fleet tools) and previews for links to 18 fleet tools, such as Docket cards and Gavel decisions.
Inbound webhooks accept plain text or a structured envelope. Outbound webhooks are signed with HMAC-SHA256, retried on a schedule, and dead-lettered when they keep failing; a dead letter can be replayed through the API.
A fleet tool can show a Chirp thread inline by giving a guest a scoped session token, so a person without a Chirp account can reply. The frame talks to its host through a documented postMessage contract.
Real captures of the running tool, with fictional StrataForge Robotics data. They follow your theme.
The first prompt creates a thread in Chirp and titles it with what you asked.
Tool calls, sub-agent summaries, and turn summaries post to the thread as they happen.
Reply from the web or your phone. Chirp queues the reply in that session's inbox.
The next hook poll hands the reply to the session, and a session that has gone quiet picks it up when its turn ends.
Chirp's web client has a skip link, labeled landmarks, a channel drawer that closes on Escape, polite live announcements for typing, and reduced-motion rules for its Instruments animations, and its tests run axe-core on three surfaces. An axe-core run over every captured view found violations the first time, mostly color contrast; we fixed them in the web client, and the latest run reports none on the desktop views and one on a phone-width view, which we list below instead of hiding it. We do not claim a WCAG level.
Partly supported
The web client has a skip link to the main content, and on small screens the channel rail is a drawer that closes on Escape. A keyboard-only walkthrough of every flow has not been recorded, and keyboard use of Instruments is a written contract that has not been tested.
Partly supported
The client has a labeled Channels region, accessible names on unread badges, polite live announcements for typing, and alert roles on errors, and two axe tests pass on three surfaces. The wider axe run over every captured view reports no violations, and nothing has been tested with a screen reader.
Partly supported
Chirp's own axe run reports no color-contrast violation in any of its 32 desktop view runs. It first found 59 elements in all 32 runs; brand-accent text, text on an accent fill, amber text, and the sidebar status prompt were raised to at least 4.5 to 1 in both themes. axe left 26 checks undecided, so contrast is not fully verified, and one element pair on the phone-width Tasks page in light mode still fails.
Partly supported
A prefers-reduced-motion rule stops the pulse on a running Instrument and the row transitions on the Instruments board. Other motion in the client is not covered by a rule or a test.
Not yet tested
Resizing text to 200 percent has not been tested.
Partly supported
Nine views fit a 375 by 667 phone screen with no sideways scrolling in both themes, and the channel rail becomes a drawer. The same run found one color-contrast violation, on the Tasks page in light mode, and tap-target size was not measured. A scrollable block that was not keyboard-focusable was fixed.
| Backend |
|
|---|---|
| Web client |
|
| Agent bridge |
|
| Messages and Instruments |
|
| Integrations |
|
| Operations |
|
| Stands in for | Slack |
Slate shows a Chirp thread inside a shared list item, so the people you share with can chat without a Chirp account.
Embedded chat can carry a Tribe contact's identity, so a guest is scoped to their own conversation.
A /docket command and previews for links to Docket cards and boards.
A read-only /gavel command and previews for links to Gavel decisions.
Chirp registers Vigil monitors for its own health.
Chirp reports logs and metrics through the Chronicle SDK.
Relays Chirp's MCP tools to agents on every machine.
An agent can read and post messages, steer another session, queue a task on a Mac, keep shared documents, and set up webhooks through Chirp's MCP tools.
get_my_identitylist_workspacesget_workspacecreate_workspacelist_workspace_membersget_userlist_channelscreate_channeljoin_channelleave_channellist_channel_membersmark_channel_readchannel_analyticslist_messagessend_messageedit_messagedelete_messagereact_to_messageunreactget_threadlist_thread_repliesreply_in_threadresolve_threadsearch_messagesset_statuslist_filesget_filedelete_filelist_agent_tasksget_agent_taskreply_to_agentqueue_agent_tasklist_queued_taskscancel_queued_tasklist_agent_daemonslist_projectscreate_projectlist_project_taskspost_to_tasklist_artifactscreate_artifactread_artifactappend_artifactreplace_artifactartifact_historylist_integrationscreate_inbound_webhookcreate_outbound_webhooklist_outbound_webhooksask_chirpyget_chirp_instructionscheck_service_healthget_diagnosticsBuilt for steering agents first. It streams every session's transcript over one WebSocket, lets you reply to a running session, starts a task on your Mac, manages the listener, renders PubMark messages natively, and has the six-lens Instruments hub, plus channels, DMs, threads, and a composer. Its README reports 413 passing tests (08/17/2026). Distribution today is TestFlight internal testing.
Chat, the agent bridge, the six-lens Instruments hub, Chirpy, search, local notifications, a menu bar extra, multiple windows, and deep links. It installs from a local script. Its README reports 426 passing tests in 60 suites, with every gated file at or above 80 percent line coverage (10/05/2026).
No. Every screenshot is a capture of the running app against fictional StrataForge Robotics data.
That is the idea. It covers channels, DMs, threads, reactions, search, files, and webhooks, and it adds the agent bridge that Slack does not have. A few Slack features are not built, and Chirp does not show read receipts.
Yes. The reply_to_agent MCP tool queues a message in a running session's inbox, the same route a reply in the web client uses, and the session reads it on its next hook poll.
The task waits and starts when the Mac wakes, and it expires after an hour by default, so an old task does not start long after you forgot it.
On the Instruments and protocol page of this site, which covers the envelope, the PubMark presentation, and what an Instrument does.
Write to Renkara Media Group and a person will answer.