Bosun Beta - MCP, clearer runs, and workflows that scale

Keeping dependencies current, following up on security alerts, updating documentation after every release, or migrating a large codebase. That work needs context, structure, repeatability, review, access control, and a clean path from signal to pull request.

Since the April update, we have been pushing Bosun further in that direction.

Bosun is getting better at the practical maintenance work teams want to run again and again, and it is becoming easier to connect those workflows to the systems engineering teams already use.

---

Automate more

We added fan-out and joins, so a task can split work across multiple branches of execution and bring the results back together. For larger codebase work where one agent pass is not enough, or where the right shape is to inspect several areas in parallel before deciding what to change.

We also added task breakpoints and a fast retry flow. Great for debugging, you can pause, inspect what happened, and continue with more context instead of starting over from scratch.

A few concrete upgrades here:

• Any tool available to agents can now be used as a concrete step in automations.
• Tasks can now be scheduled on intervals.
• Dispatch inputs are easier to inspect in the session log.
• Expected outputs are exposed while tasks render, making task behavior easier to understand before a run starts.

This is the direction we want: tasks that teams can shape, inspect, and reuse.

Automate from your favourite coding agent

“Hey Codex, automate the following with Bosun: Every time a dependabot pull request fails, automate a task for me that inspects the issue, researches an upgrade guide, and presents a fixed pull request.”

That gives teams another way to create, run, and inspect Bosun tasks from the tools they already work in. It also makes Bosun a better fit for teams that want agent workflows to be accessible through a standard interface instead of only through the web app.

More integrations and improving the way we work

GitLab support now covers release and tag reading, plus release writing. That is important for teams that do not live entirely in GitHub, and especially for companies with on-premise or self-hosted source control setups.

Project support is also much stronger. App flows are scoped to projects, project management is in place, and on-premise SSO options are available from login.

We also added task run provenance to pull requests and commits. When Bosun opens a PR, teams should be able to see where it came from and what run produced it.

Redesigned logs

The redesigned session log makes it easier to inspect what happened during a run and why.

The session log has been redesigned, token usage breakdowns are visible, and startup activity copy is clearer. Errors during task creation are more actionable. Markdown rendering and editor behavior are cleaner. GitHub installation handling is more robust.

The session log now also includes an interactive mini map, to make it easier to traverse, inspect, and understand a more complex run.

Closed beta

Bosun is still in closed beta, and we are sending more invites as we go.

If technical debt, dependency maintenance, or recurring codebase work is becoming too expensive for your team, there are a few easy ways to follow along or reach out:

• Join the mailing list: Subscribe on bosun.ai for product updates and new invite waves.
• Reach out on social: Talk to us on LinkedIn if you are dealing with maintenance, migrations, or messy dependency work.
• Join Discord: Come by the Bosun Discord if you want to follow along more closely.

Timon Vonk
Co-founder & CTO, Bosun
linkedin.com/in/timonv