MCP

File your first launch

Run /launch on a real PR to capture the full context of a code change as a Buron source.

This walkthrough runs /launch on a real code change and shows the source landing in Buron. By the end, you'll have filed a structured snapshot of a feature you shipped, and Buron's content agents will have the context they need to generate marketing assets.

You'll need the Buron MCP server connected to your editor. If you haven't done that yet, start with Connect Buron to Claude Code.

Check out a branch with changes

Switch to a branch that has real changes: a feature branch with a PR, or a branch you're about to merge. /launch reads the diff, so it needs something to capture.

git checkout feat/your-feature

If you don't have a branch ready, any branch with commits ahead of main works.

Run /launch

In your editor, type:

/launch

The agent gathers everything it can find:

  • The git diff and full commit messages
  • The PR title, body, and review comments (via gh)
  • Code comments and JSDoc around changed paths
  • Test case names (describe/it strings)
  • Screenshots and demo URLs from the PR

This takes about a minute. The agent writes a structured source file locally, then pushes it to Buron.

See the result

When the agent finishes, it confirms where the source landed:

✓ Source written to .buron/sources/claude-code/2026-05-11-your-feature.md
✓ Pushed to /wiki/sources/claude-code/2026-05-11-your-feature.md

The file also lives locally in your .buron/sources/ directory so you can review it.

The first time you run /launch in a project, the agent files a baseline source first, a ground-state snapshot of what the product does today. This gives Buron's curator the "before" for every future launch.

What happens next

The source is now in your team's knowledge layer. From here, Buron's curator agent clusters related sources into launches, assesses the launch tier, and creates tasks for content agents. You don't need to do anything: the content appears in your dashboard when it's ready.

Tips

  • Run it early, run it often. A source per PR is better than one giant source for a release. The curator handles clustering.
  • Don't worry about polish. The source is raw material. Content agents turn it into finished copy.
  • Include screenshots. If the PR has screenshots or demo videos, the agent picks them up and includes the URLs in the source.

What's next

Was this page helpful?

How launches work

The loop from code change to marketing asset. How Buron turns a code diff into a changelog, blog post, and social thread without a briefing meeting.

Automate launch filing

Set up editor or CI automation so every branch files a Buron source without anyone running /launch manually.

On this page

Check out a branch with changes
Run /launch
See the result
What happens next
Tips
What's next