Automate launch filing
Set up editor or CI automation so every branch files a Buron source without anyone running /launch manually.
Running /launch manually works well for individual features. But if you want sources filed automatically, there are two paths: editor automation and CI.
Path 1: editor automation
The fastest way to automate. Your editor runs /launch on a recurring basis while you work, with no CI config and no API keys in GitHub.
Claude Code supports routines: recurring tasks that run on a schedule. Set one up to run /launch on the current branch whenever you're working.
Cursor has background agents that can run skills automatically on a schedule.
In both cases, the /automate-launch skill walks you through the setup:
/automate-launchOnce configured, sources get filed as you work. No extra steps, nothing to commit.
Path 2: CI automation
For teams that want coverage on every PR regardless of editor, a GitHub Actions workflow runs /launch through an AI agent. The /automate-launch skill writes this workflow for you: run it in your editor and pick the CI path.
Add the two secrets
The workflow needs a Buron token and your AI provider's API key. Mint the token from your logged-in CLI and store both with the gh CLI:
buron token create
gh secret set BURON_TOKEN
gh secret set ANTHROPIC_API_KEYgh secret set prompts securely for each value without exposing it in shell history.
If you don't have the gh CLI, install it with brew install gh (macOS) or winget install GitHub.cli (Windows). Or add the secrets manually from your repo's settings page.
How it works
On every pull_request event, the workflow runs in your CI environment using your AI provider key:
- Checks out the repo
- Installs the Buron CLI
- Your agent reads the PR diff, comments, and code context, then runs
/launch - The CLI pushes the source to Buron
Buron never sees your code. The agent runs entirely in your GitHub Actions runner, and only the final source, a plain-language summary of the change, is sent to Buron.
Sources accumulate passively. The team ships PRs as normal, and launches appear in the dashboard without anyone thinking about it.
Which path to pick
| Editor automation | CI automation | |
|---|---|---|
| Setup | Run /automate-launch | Run /automate-launch, add secrets |
| Covers every PR | Only when the editor is open | Yes, automatically |
| Needs AI provider API key in CI | No | Yes |
| Runs without developer action | Yes, while the editor is running | Yes |
| Best for | Most teams, solo developers | Large teams, full PR coverage |
Editor automation is the simplest starting point. It works out of the box with no CI changes. Add CI later if you need guaranteed coverage on every PR.
Next steps
- How launches work for the full loop from source to marketing asset
- Run Buron from CI for more CI patterns beyond launches
Was this page helpful?