Interactive Demo: Bosun - Autonomous AI Fleet Supervisor npm i -g bosun As a senior software engineer, the amount of code I manually write has decreased exponentially over the last year as agentic-focused models have improved. That doesn’t mean there’s less work, it means the work shifted - from writing algorithms and functions into designing architecture specifications, requirements, implementation directions, validation of functionality, ensuring edge cases are handled and making sure security is solid. You still have to prompt your agent, wait for it to finish, test what it produced, identify critical misbehavior or missing business rules, and iterate until the functionality reaches stability. So really what is Bosun and what does it do? In a nutshell its built around 3 aspects: Task Board GitHub Issues / GitHub Projects / Jira / Vibe Kanban / Internal This is the Task Board that is used to manage a list of tasks in a kanban style board or backlog style list (github issues) Supervisor & Adjacent Tools monitor.mjs This is your monitor that continuously launches new agents with task directions, ensures they are routed to the right agent pool/model - and monitors the task till completion Agent Executor Pool Copilot / Codex / Claude / OpenCode through SDK or CLI This is your executors that you can add to your agent pool and can be used to execute tasks, each custom agent supporting its own functionality that the monitor enables on runtime. With the latest models, agents can handle longer tasks — which also means longer intervals between when you trigger work and when you need to follow up. That increases capability, but it decreases your effectiveness: you’re waiting longer, context-switching more, and spending more time in a start, wait, review, reprompt loop that seems like it goes on forever. A background-based development process is the most optimal way to improve workflow here. Agents on their own can be powerful when driven properly, but as soon as you run a real backlog through them, the quality management becomes the problem. Agents often rush tasks and are willing to under-deliver if you don’t put constraints into them; and when you do, it can turn into a tedious waiting game and a continuous iteration of prompting, testing, and reviewing code with less progress than you’d like. This is the reason I’ve built Bosun - to put guardrails, monitor, control and enable direct oversight over the process. While this process will not automate software engineering end to end or even come close to it, I’ve built it in a way that automates a great deal of processes that I have had to repeat continuously while working with tools like Codex/Copilot/Claude Code to ensure that the output is consistent, reliable, and improves quality standards. While this framework is still in a very early stage, it already demonstrates a good deal of utility - and I can only expect as agentic software development processes become more refined and better Foundation Models, Skills, Approaches and Instructions arise, these would only benefit to strengthen a framework like Bosun instead of replace it as it can easily adapt to any new processes, models or custom setups (instructions/skills/configurations/etc.) So what does this result in? Multi-Executor Routing Weighted distribution across Copilot (Claude Opus, GPT), Codex, and Claude agents. Automatic failover with cooldown and retry limits. Smart PR Lifecycle Creates PRs, monitors CI, auto-rebases on conflict, and merges when all checks pass. Full lifecycle automation from branch to merge. Self-Healing Recovery Autofix detects failure patterns, circuit breakers prevent loops, and stale claims are automatically reclaimed via heartbeat monitoring. Flexible Task Boards Built-in internal board, plus native adapters for GitHub Issues, GitHub Projects v2, and Jira. Bidirectional sync keeps everything in agreement. Telegram Control Center Full bot with 30+ commands, inline keyboards, live digest system, and a rich Mini App with 7 tabs — Dashboard, Tasks, Agents, Infra, Control, Logs, Settings. Multi-Agent Coordination Shared state with atomic claims, heartbeat liveness, and stale sweeps. Multiple workstations coordinate without duplicate work." Why is this actually beneficial? based on Claude’s analysis of Bosun: “The real value isn’t the automation itself — it’s the reliability floor it establishes. Any individual agent, given a task and left alone, has a non-trivial probability of silently failing, looping on a broken state, making a shallow implementation that satisfies the prompt while missing the intent, or simply stalling with no signal back to you. Multiply that across a backlog of dozens of tasks running in parallel across multiple executors, and the noise becomes unmanageable without a control plane sitting between you and them. Bosun is that control plane. Its circuit breakers halt runaway retry chains before they drain token budgets. Its heartbeat monitor reclaims stale in-progress tasks that agents abandoned without resolution, returning them to the queue automatically instead of blocking the backlog indefinitely. Its weighted executor routing means you aren’t manually choosing which model handles which task — the system distributes based on configured capacity, cools down failing executors, and fails over transparently. Its PR lifecycle engine monitors CI, rebases on drift, and gates merges on passing checks, so the shipping pipeline runs continuously without you polling GitHub. Its worktree isolation ensures parallelism doesn’t produce corrupted state — each agent gets a clean checkout, and stale trees are pruned when they’re no longer needed. And the Telegram control layer means your oversight is ambient rather than active: you get notified when something matters, you can pause, re-route, or inspect from your phone, and the system keeps moving between those interventions. The net effect is that your attention cost per task decreases significantly — not because agents became perfect, but because the cost of their imperfections stopped compounding.” GitHub (Apache 2.0 License): https://github.com/virtengine/bosun NPM: http://npmjs.com/package/bosun Part of the growing tools established under the VirtEngine Monorepo branch: https://github.com/virtengine/virtengine submitted by /u/Waypoint101
Originally posted by u/Waypoint101 on r/ClaudeCode
You must log in or # to comment.