Slack bot, org credentials, and start scripts
Slack integration for triggering agents from your workspace, org-scoped Claude and Codex credentials, and a new start_script repo config option.
Overview
This release ships the Slack bot integration, letting teams trigger and
receive amika agents directly from Slack. It also adds org-level
credential management so teams can share a single Claude or Codex API
key, and extends repo config with a start_script option.
What's new
- Slack integration: Connect amika to your Slack workspace from the Integrations page. Once configured, you can message the bot directly (DMs are supported, not just thread replies) and it will run an agent and post results back to the thread. Errors surface in the thread too, so you're not left guessing if something went wrong.
- Slack repo binding: In the Integrations settings, you can bind a Slack workspace to a specific repository so the bot knows which repo to operate on by default.
- Org-scoped Claude and Codex credentials: Admins can now set a Claude or Codex API key at the org level. Individual users can still provide their own key and it will take precedence, but teams no longer need every member to configure credentials separately.
start_scriptin repo config:.amika/config.tomlnow accepts an optionalstart_scriptunder[lifecycle], alongside the existingsetup_script. It runs onamika start— i.e. when you resume a stopped sandbox — making it the right place for commands that bring your app back up after a stop/resume cycle.- Better API docs: The interactive API reference now uses Scalar,
and
llms.txtendpoints are available for LLM-friendly API discovery.