Repository workflows, Slack agent picker, and TypeScript SDK
Automated repo workflows on sandbox creation, per-thread Slack agent and repo selection, a new TypeScript SDK, larger sandbox sizes, and CLI auto-detection of your current git repo.
Overview
This release introduces repository workflows that run automatically when a sandbox is created, a Slack bot upgrade that lets each thread pick its own repo and coding agent, and a TypeScript SDK for driving sandboxes from your own code. The CLI now infers your git repo from the current directory, sandbox sizes expand to L and XL, and sandbox creators are visible throughout the app.
What's new
- Repository workflows: Define TOML-based workflows per repo and edit them in a node-graph canvas. Workflows run automatically when a sandbox is created, and live workflow events stream into the sandbox page as they execute.
- Slack agent picker: When @amika is mentioned in a new Slack thread, users can choose which repo and which coding agent (Claude or Codex) to use for that thread. Channels can set defaults so common cases skip the picker entirely.
- TypeScript SDK: An
npm-installable client for the hosted HTTP API covering the full sandbox lifecycle (create, wait, agentSend, delete). The SDK version is pinned to the matching Amika CLI release and published via a gated npm workflow. - L and XL sandbox sizes: Pick larger sandboxes from the create-sandbox dialog. A tooltip shows the specs for each size.
- Sandbox creator visible everywhere: Both
amika sandbox lsand the web sandbox list now show who created each sandbox. - CLI auto-detects your repo:
amika sandbox createinfers the git repo from your current directory. Pass--git <url|path>to override, or--no-gitto opt out. The repo column is also now shown inamika sandbox ls. start.shhook: Define astart.shthat runs on every sandbox start (not just create), alongside the existingsetup.sh. Useful for commands that need to run on resume as well as initial setup.