Dashboard

The Tallpine desktop app is where you manage projects and sessions. Open a worker's Chat or terminal, review its pull request and changed files, and preview its web app.

The app shell

Tallpine remembers the session's committed interface mode. Opening a Chat session restores its paged conversation timeline; opening a TUI session reconnects to its terminal through the daemon mux.

Open Automations from the sidebar to create recurring work, edit its prompt and schedule, enable or pause it, delete a definition, and inspect run history. Local schedules run in the daemon: keep the host awake and Tallpine running. See schedule behavior.

Projectless standalone tasks do not need a Git project. Cloud sessions appear only when the build and account enable that integration; their execution and data live remotely.

Read session state

Tallpine does not persist a display-status label. It derives what you see from durable facts such as agent activity, termination, controller state, and current pull-request checks, reviews, and mergeability.

Common activity signals include:

• Active: the controller is currently working.
• Idle: it is alive and ready for another instruction.
• Waiting for input: the agent is at an empty prompt and can receive a follow-up.
• Blocked: an approval or permission decision is pending; automation will not inject input.
• Exited: the controller reported that it ended.

A failed or unknown runtime probe alone is not proof that a session is dead.

Work in Chat

Chat sessions show durable messages, provider activities, commands, plans, changed files, approvals, structured questions, usage, and compaction state. History loads in bounded pages so long-running sessions remain responsive.

The composer sends a provider turn through the daemon. A Chat session can also open a session-scoped worktree shell without creating an agent TUI pane.

Chat controls depend on the provider. Where supported, choose a model, reasoning effort, and permissions; attach images; inspect skills and Model Context Protocol (MCP) tools; and use slash commands such as compaction. Session links and reported artifacts keep related work together.

Run a cue sends a saved project instruction or opens a shell command in a fresh terminal. See Project settings.

Work in Terminal UI

Terminal UI sessions keep the selected agent's native terminal experience available through Tallpine. New macOS/Linux sessions use Tallpine's native terminal host. Older sessions and fallback launches can use tmux. Windows uses ConPTY.

Use the terminal for native prompts and interactive tools. Use Tallpine's message controls for routine follow-ups so lifecycle reactions can apply the correct delivery policy.

Switch interfaces

Supported sessions show Switch to chat UI or Switch to terminal UI. Which action appears depends on the agent, the current interface, and whether it is working. Tallpine keeps the same session and worktree and replaces one controller at a time.

When offered, Finish work, then switch waits for accepted work. Stop now and switch interrupts it. Some terminal sessions require Terminate and then switch. Read the dialog before continuing because drafts, attachments, or queued turns may need to be sent again.

Where supported, Tallpine can resume the same provider conversation in Chat. It does not turn old terminal screen output into Chat messages.

Pull requests and reviews

Once a session has a linked pull request, the inspector shows a concise summary:

• Pull-request identity and link.
• CI state, including failing check names and links.
• Reviewer information and unresolved-review counts.
• Mergeability and reasons the pull request is not ready.

Tallpine can run configured reviewer agents, send review findings back to the worker, resolve review comments, and request a merge. Raw CI logs and full review bodies are not part of the concise desktop summary.

Enable Auto review for one session, or set the project default for new sessions. Tallpine starts a review only when the pull request is eligible and the worker is idle. This does not enable automatic merge.

In Files, choose workspace changes or pull-request changes. You can inspect commits where available. Looking at local changes does not publish a review to the repository.

Browser preview

The Browser tab displays the preview target explicitly selected for the session with tallpine preview, tallpine preview <url>, or tallpine preview start. The default temporary browser profile is isolated per session. Named browser profiles persist cookies and storage and can be reused across sessions; sessions using the same named profile deliberately share that browser state.

Tallpine's browser bridge can support agent-driven navigation, snapshots, clicks, typing, screenshots, console inspection, and temporary network-metadata capture. Network capture is off by default, bounded, omits bodies and sensitive values, and expires automatically.

Use the Browser toolbar to select a profile, open DevTools, pop out the view, or annotate the page and send feedback to Chat. Orchestrators can open a browser on demand. Keep the panel visible for screenshots and human-style pointer actions.

In Settings → Browser, manage named profiles and downloads. Import can copy supported data from Chrome, Firefox, or Safari into Tallpine-owned storage; availability and cookie support vary by OS/browser. Tallpine reads the source profile without modifying it, and not every login transfers. Deleting a Tallpine profile removes its saved browser state; choosing a different profile changes the cookies used by the view.

Notifications

The notification center keeps alerts for sessions that need input, pull requests ready to merge, merged pull requests, and pull requests closed without merging. Open the bell to see the newest alerts first, then choose one to open its session or pull request.

Opening the panel marks loaded unread alerts as read, but leaves them in the feed. Use Clear all or an alert's clear control to remove records. Scroll down to load older alerts. There are no separate Unread/All tabs or individual mark-read buttons. Tallpine also shows desktop toasts while it is running.

Connect Mobile

In Settings → Connect Mobile, enable access and wait until pairing is ready before scanning the QR in the mobile app. Tallpine advertises available LAN, Tailscale, or managed remote-connector addresses. The primary desktop API stays on the local computer. See Connect Mobile for pairing and transport details.

Paired phones can receive push notifications when they have permission and the daemon can reach the push service. Turn notifications off on the phone, or remove it in Connect Mobile. On supported Macs, Keep awake can help keep the computer reachable.

Project settings

Project settings configure worker and orchestrator roles without changing the registered repository identity. The desktop app writes through the daemon API; it does not directly edit the database or run session logic in the renderer.

GitHub and GitLab provide pull-request and issue data. Cues belong to a project. Create a Cue to save an agent instruction or shell command. An agent Cue sends a prompt to an eligible session or starts a worker. A blocked session cannot accept an ordinary prompt. A command Cue runs the exact command in a fresh local terminal; it does not ask an agent to interpret it.

Use General to choose the default session interface. Harness shows setup and readiness. Subscriptions manages agent accounts such as Codex device accounts. See Settings and views. Browser manages profiles and downloads. Project settings hold role-specific model, effort, permission, and rules overrides.

Closing a terminal or switching views does not archive a session. Some detached terminal and Chat processes can survive a daemon restart; reconnecting depends on the computer and provider state. Archive ends the Tallpine session. Stopping only its agent leaves a session you can resume. See session commands for resume, restore, and cleanup.

Next steps