Practical overview
When it fits
Use BOSS Console when an agent task spans web research and local development tools, or when you want to monitor an agent's work in the same workspace it uses. For always-on use, keep BOSS and the agent running on a machine that stays online.
Who it is for
- Developers who want an agent to work with browser pages, commands and code in one visible workspace.
- Researchers who need to keep research material beside an agent session.
- Teams building or operating agents with configurable plugins and MCP tools.
Documented uses
- Run an always-on agent in a desktop workspace.
- Give an agent access to browser, terminal, editor and selected plugin tools.
- Inspect terminal output, open files, navigate browser tabs and review visible work.
- Organize projects and activities using split panes and saved Spaces.
- Connect an existing supported coding-agent CLI through the console's MCP tools.
Requirements & limits
The project lists desktop downloads for macOS, Windows and Linux. Fluck agents can be revisited through fluck.ai; shared terminals and BOSS windows are accessed through cli.risaboss.com after signing in with the same BOSS account, with access depending on sharing settings. BOSS Console is open source under Apache-2.0.
- BOSS is a native JVM-based console built with Kotlin and Compose Multiplatform, not an Electron app.
- Tool availability depends on installed plugins and access settings.
- Always-on agents require BOSS and the agent to remain running on a machine that stays online.
- The project supports Fluck Agent and names Claude Code, Codex, Gemini CLI and OpenCode as connectable coding agents.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect an existing coding agent to BOSS tools
Connect a CLI agent to BOSS so it can call tools exposed by active plugins.
Before you start
- BOSS Console
- A CLI agent such as Claude Code, Codex, Gemini CLI, or OpenCode
- A BOSS terminal and the desired tools available through installed plugins
Steps
Open a BOSS terminal.
Connect the CLI agent through Toolbox → MCP or the BossTerm AI menu.
Choose which BOSS tools the agent can call.
Expected outcome
The CLI agent can access selected BOSS tools; available tools depend on installed plugins and access settings.
Guide limitations
- The local boss MCP server discovers tools from active plugins, so the available tool set depends on which plugins are active.
- The README notes that other agents and tool policies may behave differently.
Set up a persistent Fluck Agent workspace
Create an always-on Fluck Agent with selected workspace tools and keep it running on an online machine.
Before you start
- BOSS Console
- A machine that stays online
Steps
Use Fluck Agent in BOSS to create an agent for your projects or everyday work.
Give it access to the browser, terminal, editor, and plugins it needs.
Keep BOSS and the agent running on a machine that stays online.
Expected outcome
The Fluck Agent remains running in BOSS, and you can return to your Fluck agents from another device at fluck.ai.
Guide limitations
- Access to shared terminals and BOSS windows depends on sharing settings.
- The README does not specify detailed account or installation prerequisites.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- risa-labs-inc/BossConsole · Official homepage title · retained in its source language