Snapshots, Slack upgrades, and developer tools
First-class sandbox snapshots with secure capture and per-repo defaults, per-workspace Slack settings with gate cards and grouped sandbox view, zero-config Playwright MCP, and Cursor SSH aliases.
Overview
This release makes sandbox snapshots a first-class feature: capture, label, and reuse sandbox state as a starting point for new sandboxes, with credential scrubbing baked in. The Slack integration gets per-workspace settings, a configurable system prompt, interactive gate cards before dispatching an agent, and a grouped sandbox view tied to the originating Slack conversation. Developer tooling adds zero-config Playwright MCP and stable per-sandbox Cursor SSH aliases.
What's new
Snapshots
- Snapshot management: Create, label, and browse snapshots from the sandbox page. Sandboxes track which snapshot they started from, and you can pick a saved snapshot when creating a new sandbox.
- Per-repo default snapshot: Repositories can configure a default snapshot that new sandboxes use automatically. You can override or skip it per sandbox.
- Secure capture: Credentials, env files, and agent data directories are scrubbed before a snapshot is saved. A snapshot-and-delete flow in the UI makes the process explicit.
- Reliable activation: Snapshot timeouts are raised (15 min capture, 10 min activation). If capture fails, the sandbox stays active.
Slack
- Per-workspace settings: Each connected Slack workspace now has its own settings page for repo binding, agent defaults, and a custom system prompt.
- Gate cards: The bot posts an interactive card before dispatching an agent, so you can confirm, redirect, or cancel from Slack.
- Grouped sandbox view: Sandboxes are grouped by the Slack workspace and conversation that created them, with workspace branding and the triggering thread shown inline.
Developer tools
- Playwright MCP: Playwright is available as a zero-config integration in all sandboxes, running headless with no setup required.
- Cursor SSH: A stable per-sandbox SSH alias lets you open Cursor directly into any sandbox and reconnect after restarts.
amika sandbox ls --long: The sandbox list is trimmed by default; pass--longto see all columns.
Reliability
- Claude OAuth tokens are refreshed server-side before injection. If a token is dead, the UI surfaces a re-auth error rather than silently failing.
- SSH access tokens include sandbox ID and name and are valid for a full working day.
- Sandboxes return to active state after a failed snapshot attempt, so you don't lose your work.