SideButton Portal: Orchestration for a Fleet of AI Coding Agents

Max Svistunov — Mon, 03 Aug 2026 07:11:00 +0000

SideButton Portal is an AI agent orchestration platform for coding agents: roles, playbooks, monitoring, and integrations in one place. It is live now, and it plugs into the Jira and GitHub your team already uses.

A product lead runs the fleet

The fleet is a cross-functional development team of autonomous teammates that pick up tickets and carry them to completion on their own. The product lead owns the intent, the fleet owns the execution.

The intent comes first, before any code exists: pin down the problem, sketch the end state, hand the epic over. From there, every ticket runs the loop in the picture. Coding: an agent writes the change. PR Review: a second agent accepts it only when it holds up. QA Live: a third agent opens the product like a user and proves it works. Out comes a pull request that has been reviewed and tested, ready for the team to accept.

Running the fleet means reading flags, not code. Done is a claim, and the fleet checks it. Work that passes ships, and work that does not comes back as a question.

The loop keeps no office hours. It is still working after the office logs off and further along by morning. Supervision does not disappear, it moves up a level, from reading code to setting direction.

What the Portal adds

Compose your team. Software engineer, QA, PM, and senior review come built in, and you can add roles of your own. Junior agents do the work, a senior agent reviews it, and you approve last.

Connect your tools. Jira, GitHub, Slack, your cloud, your choice of model. The Portal fits into how your team already works rather than asking it to move.

Define the work once. Playbooks run whole jobs end to end. Bug fix, feature implementation, and hotfix are ready on day one, and you can build your own. Every step is recorded.

Watch everything live. See what any agent is doing right now, follow a job step by step, and know what each one costs.

The engine is open source

Inside every agent is the open-source AI agent MCP server that anyone can run on a laptop today. The Portal is the layer around it, the part that turns individual agent output into company output you can stand behind.

Start today

Everything above is a claim, and you already know the rule for claims: check them. Connect Jira and GitHub or Bitbucket, drop the first tickets in, and read what comes back. Pin down the problem, sketch the end state, hand the epic over.

Put AI coding agents on your team.

Originally published at sidebutton.com.

SideButton: An Open-Source MCP Server for AI Coding Agents

Max Svistunov — Fri, 31 Jul 2026 15:02:11 +0000

SideButton is an open-source AI agent platform built around an MCP server. It gives any coding agent a real browser, a workflow engine, and reusable domain knowledge. Version 1.5 is out, and all of it runs on your own machine.

What is in the box

MCP server. Built-in tools for real-browser control, workflow execution, run logs, and artifacts. Claude Code, Cursor, Copilot, and Windsurf connect over stdio or HTTP + SSE, with MCP OAuth 2.1.

Workflow engine. Agentic workflows defined in YAML, with step types spanning browser actions, shell commands, LLM calls, and control flow, plus nested workflows and retries.

Knowledge packs. The domain knowledge that turns a general coding agent into a software engineer, QA engineer, or product manager for one specific app. Selectors, data models, workflows, and built-in roles per web app.

REST API and dashboard. A REST API so any webhook, cron job, or internal tool can trigger a workflow, plus a local dashboard with live run logs and a pack manager.

Tracker and chat steps work across Jira, Linear, GitHub, and Slack. The LLM provider is auto-detected from your environment.

Getting started

Install the server:

npx sidebutton@latest

Connect the SideButton Chrome extension, then point your agent at the server:

claude mcp add sidebutton --transport http http://localhost:9876/mcp

Install a knowledge pack for the web app you work on with sidebutton registry add, or scaffold your own with sidebutton init. Packs land in ~/.sidebutton/skills/ and load on startup.

From there the agent works on its own: running workflows, calling the LLM where reasoning is needed, logging every step. Your browser, your sessions, your API keys, all local.

Knowledge packs are just markdown

A pack is a folder of markdown files, so it reviews and diffs like code. You can ask Claude to capture what it learned during a session, or scaffold a pack with sidebutton init, then share it through a registry that is either a local folder or a git repo. Installed packs merge their workflows, roles, and domain targets into your local config at startup.

Plugins add your own tools

The MCP server is extensible in any language. A plugin is a folder with a manifest and a handler script under ~/.sidebutton/plugins/, loaded alongside the built-in tools at startup. Two ship in the box: screen-record, which captures an agent session to MP4, and writing-quality, which scores content before it goes out.

What is next

Native iOS and Android apps, and a public registry so teams can discover and share knowledge packs instead of rebuilding them.

The platform is stable and open source today. Browse the AI agent skills already published for popular web apps, or write one for the app your team lives in.