Linear integration, a new SSH layer, and cross-repo snapshots

Overview

Amika works in Linear now. Assign a ticket and it reads the issue, picks the repo, does the work, replies in the thread, and moves the ticket across your board.

Sandboxes get a rebuilt SSH layer with per-user key authorization, services you can expose at any time instead of only at creation, and snapshots that are no longer tied to the repository they were captured on.

The web app also works on mobile now, so you can kick off a run or check on one from your phone. Web terminal and web chat for agents are coming soon.

What's new

Linear

• Assign a ticket to start a run. Amika moves it from To Do to In Progress when it picks up the work, and to In Review when it finishes.
• It reads the ticket. The issue title, description, and labels go into the first turn, so the agent works the actual ticket instead of a bare mention.
• repo: labels route work. Label an issue repo:api and Amika works in that repo, overriding your org default.
• One sandbox per ticket. Every comment on an issue shares a single sandbox and one continuous agent context, so follow-ups pick up where the last one left off.
• Connect from the integrations page, where you can also set the default repository and coding agent for tickets that don't specify one.

SSH

• A real SSH layer. amika sandbox sshv2 opens an interactive shell, or runs a single command with amika sandbox sshv2 <name> <command>. amika scpv2 copies files, and sftp works too. Your ssh flags pass straight through, so port forwards work like they do anywhere else. Running a one-off command and copying files both failed on the old layer.
• Per-user key authorization. Access is granted by public key per user, so you control exactly who can reach a sandbox.
• Manage your SSH keys from the new settings page, or stay in the terminal: amika secret ssh-keygen creates and uploads a key, and amika secret ssh-key list and delete handle the ones you already have.
• Cursor, Claude Desktop, and Codex all open from amika sandbox codev2.

Sandboxes

• Create services on the fly. Sandbox services used to be fixed at creation time. Now amika service create exposes a new service on a running sandbox and gives it a real URL.
• Snapshots work across repos. A snapshot used to be locked to the repository it was captured on. Now any snapshot can start any sandbox, so one setup can be shared across all your repos. Manage them under Settings, Sandboxes.

Elsewhere

• No more GitHub PATs. Connect your GitHub account and start creating sandboxes. There's no personal access token to generate, paste, or rotate.
• Personal API keys, alongside the organization-scoped ones, so sandboxes and agents act as your user with your settings.
• --output json on the CLI commands that return data, in the same shapes the API returns. Commands that open a shell, an editor, or a browser stay interactive.
• The web app works on mobile. The dashboard, sandbox pages, detail panels, forms, and menus all lay out properly on a phone instead of squishing.
• In-app support chat, reachable from anywhere in the app.