A small technical team with one person willing to keep a Mac running and set the environment up, and everyone else asking in Slack. Our first team customers are technical founders who set it up, and the designers and product people on their teams who use it without ever opening a terminal.

Ask in Slack. The agent works in a session on the team's Mac and answers in the thread, with files when it made some. If it has a question, it asks you there or on your phone. You install nothing. A designer on one team has run her design work this way for weeks.

On a Mac you own: on a desk, or a Mac mini in your cloud account. Server, terminals, agents, files and your agents' accounts stay there. Our relay carries encrypted requests between your team's devices and that Mac; it runs no agents and holds no terminal state. Your prompts still go to your model provider.

Not today. Push is Mac-only, on Apple Silicon and macOS 26. If your team cannot keep a Mac running, Push is not for you yet.

One afternoon for one person: install, sign in, connect Slack, decide who may do what, invite the bot. Push creates the Slack app for you; you approve the install in Slack and paste the two tokens it issues. The first teams are onboarded by hand, with us. The team setup guide has every step.

No, and yes. The tracker got smaller because its user changed: Push's board has three columns that follow what happened, because an agent doesn't negotiate priority or sit in triage. Keep your tracker. Link a Linear ticket to a session and the agent reads it, writes updates and state back, and a comment on the ticket reaches the session working it. Push never imports or mirrors Linear, and a Linear ticket never starts work by itself.

It stops and asks. The tab turns to needs you, the question goes to the person who can answer it, in the thread and on their phone, and the session continues when they reply. The operator can open the tab at any time.

Claude Code, Codex, OpenCode and Hermes, each on the plan you already have. Push ships no model and no agent of its own.

Transcripts stay on the Mac, in each agent's own store; Push never uploads them. Signing in stores your identity and a random fingerprint so your devices and teammates can find your Mac. The relay carries encrypted requests. Slack carries what you send the bot and what it posts back. Your agents send your model provider what they always did.

A technical person can wire Slack to Claude Code in an evening; one of our customers did. The hard part is everything after: who asked, which session, what came back, who may do what, and what happens when the Mac restarts. That is what Push is.

Those run your work in the vendor's cloud. Push runs the Claude Code or Codex you already pay for, on a machine you control, with your whole environment present: your files, your tools, your MCPs. Inference still goes to the provider.

Requests wait and are delivered when it reconnects; in Slack the bot says it is not connected. Keep the Mac awake with Always On, and keep Push open. Push does not run as a daemon.

Yes, push, bundled with the app, with the /p skill for the agents. push status, push track, push slack setup, push workspace setup check, push audit export. Same verbs for you and your agents; push --help for the rest.

Because it shows everything. A chat UI guesses what you want to see and hides the rest. Teammates never need the terminal; Slack is their window. The operator keeps the terminal to see exactly what an agent did.

Closed-source, signed, notarized binary today. Documentation of the architecture and the integration playbooks is being opened up. No commitment yet on the source itself.

Nothing. Every current feature is free for every person on your workspace, with no seat meter. Your agents bill you directly. Full pricing.