Sync Knowledge with your codebase

The Buron CLI connects your codebase to Knowledge. When engineering ships a feature or wires up tracking, the Agent has the full story without you having to write it up.

You'll need the CLI installed and your project linked. To set that up, check out Install the Buron CLI.

Snapshot a code change with /launch

When you ship a feature, type /launch in your AI editor. The skill captures everything around the change: the git diff, the PR description and review comments, and any screenshots you've shared in the conversation. It saves all of this as a structured snapshot in Knowledge.

The snapshot lands in your release pages and updates any product or feature pages it touches. From there, the Agent has the context to draft the launch announcement, set up campaigns, or prep PR pitches.

To learn more, check out Use Buron in your AI editor.

Set up tracking specs with /setup-google-ads-tracking

When you wire up conversion tracking, type /setup-google-ads-tracking in your AI editor. The skill walks you through what to track, audits your codebase, and writes the tracking spec into Knowledge.

The spec becomes the source of truth for your conversions. Buron reads from it across reports, findings, and automations.

To learn more, check out Set up your conversion tracking.

Sync from CI

For things that should always reflect what's live, run the CLI from CI. A common pattern is snapshotting your changelog or release notes when a build succeeds. The Agent picks up the new content the next time someone asks.

To set up a CI workflow, check out Run Buron from CI.

Your editor decides what gets sent

Buron doesn't have access to your codebase. Your AI editor does. When you run a slash command, the agent in your editor reads the relevant files, builds the snapshot or spec, and pushes that to Knowledge.

What lands in Knowledge is the curated artifact: a snapshot, a tracking spec, a release note. The raw source code itself stays in your repository.