Skip to main content
An automation hands a task to a coding agent. Each time one of its triggers fires, Superlog starts a fresh sandbox, checks out your repositories, and runs the agent on the task.

What starts a run

You can also start a run by hand with Run now, or try one out with Test. An automation can have up to 10 triggers. See Triggers.

What the agent can do

  • Read and change your code. Up to 10 GitHub repositories are checked out in the sandbox. The agent can run commands, tests, and builds there.
  • Use your tools. Connectors give the agent Slack, Sentry, Datadog, Linear, custom MCP servers, and workspace secrets.
  • Follow your playbooks. Skills add reusable instructions and scripts to a run.
  • Open pull requests. Pull requests from runs are listed under PRs. Review comments on them continue the run that opened them.
  • Report back. The agent replies in the Slack or Discord thread that started the run. It can also post to Slack channels and create Linear issues. Other runs can send results to Slack notification channels.
  • Take follow-ups. Reply in the run, or in its Slack thread, and the agent continues in the same sandbox with the same context. See Runs.

What teams automate

Each of these is a template. See Templates.

Models

Every automation picks its model and agent harness: Codex, Claude Agent SDK, or OpenCode. Runs can use your own API keys, your ChatGPT subscription, or the usage included in your plan. See Models and harnesses.

Limits