---

One workspace for the whole task

Keep the page you are researching beside the agent working on it. Run commands, inspect files, review changes, and arrange everything into split panes and saved Spaces.

BOSS runs on the JVM with Kotlin and Compose Multiplatform. Its browser, terminal, editor, and other tools come from dynamic plugins, so the workspace can grow with the work.

_{A real macOS workspace: a 2048 board beside Fluck Agent looking up tools. This capture shows work in progress.}

Explore Spaces and everyday use →

Run any AI coding agent

Claude Code · Codex · Gemini CLI · OpenCode

Bring the CLI you already use. Open a BOSS terminal, connect it through Toolbox → MCP or the BossTerm AI menu, and choose which BOSS tools it can call. The local boss MCP server discovers tools from active plugins, including browser, terminal, editor, Git, and automation tools.

An agent can inspect the running workspace and act in it: read a terminal's output, open a file, navigate a browser tab, or run a command. The available tools depend on your installed plugins and access settings.

From page context to visible results

1. Give the agent context. In this Fluck Agent example, the current BOSS webpage is attached to the conversation while staying visible in the neighboring pane.

_{These three product captures show BOSS 9.5.19 on Linux. The current release may look different.}

Connect your agent → · See the complete walkthrough →

Build your own toolbox

Install the tools you need from the built-in Toolbox. Browse plugins, manage updates, enable or disable tools, and customize the workspace around your project.

_{Development setup in BOSS 9.5.32 on Linux: review the selected tools before installing them.}

Start with a browser, terminal, and editor. Add Docker or Kubernetes for infrastructure, notebooks for research, automation for repeatable browser work, or your own plugin.

Tool Creator scaffolds a plugin project. Tool Evolver helps inspect and improve an existing tool. Many plugins hot-reload while the host stays open; infrastructure updates can require a restart.

Discover and manage plugins → · Build a plugin → · Browse the ecosystem →

Your workspace, on another device

Open cli.risaboss.com →

Sign in with the same BOSS account to find your shared sessions. The portal separates terminals from application windows, so you can open the kind of session you need.

Full-window sharing publishes one encrypted video stream per window through Cloudflare Realtime SFU for multiple viewers, with encrypted remote-control messages. Same-account access and automatic control are enabled by default for fresh preferences; saved opt-outs are preserved. The account backend remains trusted for admission and key delivery.

Sharing setup, access settings, and protocol diagram →

You decide what your agents can touch

Choose the tool access that fits the task through Toolbox → MCP.

• Per-tool switches remove disabled tools from the agent's available BOSS toolset and block calls to them.
• Roles and permissions govern tools that declare permission requirements. Admin users bypass role checks, but still obey the per-tool switches.
• Secret Manager supports credential references and browser autofill so supported calls can use a credential without placing its value in the agent transcript. Explicit secret-read tools have different behavior.
• Signed store plugins bind the plugin identity, version, and JAR content. A valid signature establishes provenance, not that a plugin is safe.

These controls apply to calls through BOSS. They do not sandbox an external agent, and plugins run in the host process. Disabling a tool does not cancel work already authorized. An authorized page or tool receiving a secret can still expose it.

Security and privacy → · Secret-reference guarantees → · Infrastructure plugin audit →

---

Downloads

Install BOSS, sign in, then use Toolbox to choose your initial tools.

On macOS:

brew install --cask boss

For installation scripts, platform notes, and your first workspace, follow the Getting started guide. Download links resolve to the latest stable release; use all releases to choose a specific version.

Documentation

The BossConsole wiki is the product guide. Start with a workflow, then follow its links into the technical references.

Technical references, architecture, and benchmarks

• CLI reference and Plugin Launchpad
• Core subsystems and host plugin platform
• Design system and visual styleguide
• Editor architecture, application features, and keyboard shortcuts
• RBAC guide, secret references, and dated infrastructure guardrails audit
• Browser benchmark report and reproducible harness and evidence

Development

Use JDK 17 and the included Gradle wrapper. Begin with CONTRIBUTING.md for setup, validation, and the contribution workflow. Pull requests target dev.

git clone https://github.com/risa-labs-inc/BossConsole.git
cd BossConsole
git switch dev
./gradlew showVersion

Browser and backend features need local configuration. Follow the development guide for local.properties, build commands, and isolated testing. Repository-specific instructions live in AGENTS.md.

Install the BOSS CLI through Toolbox → Tools → Install BOSS CLI to inspect and operate the running workspace:

boss status --json
boss doctor
boss mcp list --filter browser
boss file README.md

Complete CLI reference → · Plugin authoring and MCP →

Open source & ecosystem

BOSS is licensed under Apache-2.0. The host and tools live in separate repositories; plugins release independently.

Core plugins: Fluck Browser · Terminal · Editor

Support

Report an issue · Troubleshoot · Enterprise inquiries

---