BOSS Console: a persistent workspace for tool-using agents

BOSS Console combines an agent with a browser, terminal, editor and plugins in a desktop workspace. Its official page describes creating a persistent Fluck agent or connecting an existing agent CLI, then choosing the tools it can use.

Keep the workspace running

BOSS describes an always-on setup that depends on the host machine remaining online. Users can return to a Fluck conversation through the web or inspect shared terminals and windows according to their sharing settings.

That makes the operating conditions part of the feature. Before delegating a longer task, check what happens when the host sleeps, loses connectivity or the agent needs input. A remote view is most useful when it makes the current work and pending decisions understandable, rather than merely showing that a process is still running.

Choose the exposed tools

Plugins can add interfaces for people, named MCP tools for agents and services for other plugins. The page describes role-based access, plugin gates and individual tool controls, with disabled or denied tools removed from the exposed toolset.

The site also states a boundary: BOSS policies govern calls through BOSS tools, and revoking access does not cancel previously authorized work. This is important when planning a stop or a permissions change. Review the ongoing task as well as the list of tools available for the next action.

Evaluate the actual session

BOSS lists macOS, Windows and Linux support and an Apache 2.0 core. Its product examples identify captured screenshots and version-specific setup details; available tools can vary by version and account.

For a first session, use a small project with a clear expected result. Keep the source beside the conversation, inspect tool actions and test how a person takes over when necessary. The page’s credential-handling description applies to supported tools; it should not be generalized into a promise about every external agent or process connected to the workspace.