Core concepts

Push is a terminal first. Everything else exists so that what happens inside your terminal tabs — agent sessions — stays findable, resumable, and visible from anywhere.

Tabs & sessions

A tab is a terminal pane. When you run a code agent in it, the tab holds a session — the agent's conversation. Sessions are the thing Push refuses to lose: quit the app, update it, reboot, and each tab comes back attached to the same conversation. Tab statuses tell you what needs you: Active, Running, Sleeping, Shared.

Folders (and why a folder is an agent)

Tabs group by working directory into folder chips. A folder you keep working in can be tracked as an agent — a standing bench for that project. That's the whole org model: no hierarchy, just "this folder is where this kind of work happens." Your iPhone shows the same folders, and voice captures are filed into the right one automatically.

Issues

An issue is the unit of tracked work — a title, a timeline of comments and recordings, a status (Active · Completed · Archived · Deleted), and a reference built from your workspace's issue prefix (Settings → Workspace). Issues appear three ways: you write one (⌘N), you capture one by voice from the phone, or you track a session that grew into real work.

Runs

An issue can be run. The button on an issue says what will actually happen:

• Run — start a fresh agent session for this issue.
• Open — jump to the terminal tab already bound to it (● live, ◌ asleep).
• Reopen — continue the issue's previous session.
• Waiting — a run was accepted and its terminal hasn't opened yet.

One tab answers for one issue. When a conversation drifts into a second topic, you don't relabel the tab — you spin off a new issue that carries the context.

The feed

The Sessions feed is where agent activity meets you: Needs your decision (approval requests — approve or reject from the Mac or your phone), Draft ready cards (content an agent prepared for you to use), artifacts, alerts, and recent activity. Empty state is the goal: "All clear."

Artifacts

Files your agents produce — and files you ⌘-click in a terminal — collect in Artifacts, viewable in-app and publishable as revocable links.

The iPhone

Two products in one app: capture (voice in, structured issue out — works offline, on a plane) and a companion for everything above — live terminal mirrors, approvals, notifications tuned so your phone only speaks when you're away. See the iPhone app.

The words Push uses

• Capture — new work enters the system (typed, voice, browser, share sheet).
• Track — an existing session becomes an issue.
• Spin off — a live session buds a follow-up into its own issue, with context carried over and both sides referencing each other.