A side chat for your coding agents

Ask about the work.
Don't interrupt it.

Aside finds the Codex, Claude Code, Pi, and OpenCode threads already on your Mac. Pick one and ask a separate model what changed, why it chose that path, or what it needs next.

Preview for macOS · Signed and notarized

Aside
All agents3 recent · 17 total · fleet conversation

What needs me right now?

Aside

Prepare the release ended its latest turn 12 minutes ago. Review the migration is waiting for a rollback choice.

Ask across all agents…ChatGPT · fleet

Your agents already run in parallel.

Your attention doesn't.

The useful layer beside the work

Dashboards show status. Aside lets you ask why.

It does not launch agents, steer them, or merge their context. It reads the transcripts they already keep and gives you a second conversation about the work.

01

A clear read on the day

Open Today. Get the day's recap.

Open Today and Aside prepares a concise recap from the work your agents recorded that day. Projects and threads sit underneath it, with waiting and ready-to-review states easy to scan.

You choose whether Today can send a limited, redacted set of relevant activity to a cloud model. The recap and its evidence links are saved locally on your Mac.

Usage sits beside Today. Open a 90-day or one-year view of token and model activity across Codex, Claude Code, Pi, and OpenCode where logs expose it. Cost figures are API-equivalent estimates, not invoices; local runs show local-model equivalents.

02

Search the work, not just the title

Find the thread from what happened inside it.

Search prompts, agent replies, commands, file paths, failures, and Aside side chats across Codex, Claude Code, Pi, and OpenCode—even older work. The index stays on your Mac.

Subagent work stays attached: Codex and Claude Code subagents fold beneath the task that spawned them, with a transcript and side chat of their own.

03

Read is not resolved

Opening a thread doesn't make it done.

Aside keeps attention items visible after you open them, with the status, local context, and time waiting. Opening alone never clears finished, failed, or interrupted work. Mark it reviewed when you're done. Direct input stays until the agent moves on.

When a live session asks for input, Aside can also send a Mac notification.

04

One session. One side chat.

The second conversation persists.

Every discovered session keeps its own conversation and model choice. Close Aside, switch projects, and continue where you stopped.

Observer, never operator

Read-only is a boundary, not a slogan.

Aside can read supported agent transcripts and ask an observer model about them. It cannot send a message to an agent, edit a project, or run a command.

01

Search and history stay on this Mac.

The searchable index, thread list, and every side chat are stored locally with user-only permissions. Search queries never leave your machine. OpenCode sessions use a private, rebuildable local transcript cache; Aside prunes an entry when it observes that session being deleted in OpenCode.

02

Cloud context is scoped.

A session chat sends only that session to the model you chose. Common credential patterns are redacted first.

03

Provider access stays with the client.

Aside can use your existing Codex or Claude Code sign-in, Pi routes, and audited OpenCode 1.18.15 routes. It stores only your permission and the route chosen for each thread between runs. OpenCode requests run tool-free without user/project config, external plugins, custom endpoints, or shell API-key variables. Zen routes need no credential; API-key routes use the selected provider credential configured in OpenCode. OAuth and well-known routes are not supported yet.

Need transcript context to stay entirely local?

Choose an installed Ollama model for that side chat.

A native Mac utility

Install once. Keep working.

Drag Aside to Applications and open it. It lives in your menu bar, stays out of the Dock, and downloads future signed updates inside the app.

FileEditView···9:41

Reads sessions from

X CodexC Claude Codeπ PiO OpenCode

Open source · MIT

Aside is open source.

Aside reads local agent transcripts, so the code that does it is public. Read the source, build the app yourself, report an issue, or send a patch.

View the source on GitHub

Before you install

Straight answers.

Does Aside control my coding agents? +

No. Aside is a read-only observer. It cannot message an agent, edit your project, or run commands.

Does everything stay local? +

Your thread and content-search indexes, plus side-chat history, do. When you choose a cloud model, Aside sends scoped, redacted transcript context to that provider. Choose Ollama to keep model context local.

Do the coding tools need to be installed? +

Aside can discover supported session history already stored on your Mac. To use a coding client as the model for a side chat, that client must also be installed and configured. OpenCode provider access currently requires the audited OpenCode 1.18.15 client; credential-free Zen routes work without another account.

Do I need separate API keys? +

No separate keys go into Aside settings. It can use Codex's existing ChatGPT sign-in, Claude Code's existing Claude account, Pi routes, or audited OpenCode 1.18.15 routes. Configure provider access in those clients. For OpenCode, credential-free Zen and provider API-key routes are supported; OAuth and well-known routes are not. Aside isolates only the API credentials needed for model discovery or the selected route and never modifies OpenCode's canonical auth file. Routes that depend on user/project config, external plugins, custom endpoints, or shell API-key variables stay unavailable.

Which agents are supported? +

Aside currently discovers Codex, Claude Code, Pi, and OpenCode transcripts stored on your Mac.

How do updates work? +

After the first signed install, Aside downloads future signed updates inside the app and asks you to restart when one is ready.

Aside for macOS

Know what needs you.

Then ask why.