Unfair server kick from a hackathon
We can't even say moderator if they are doing any mistake?
Please view my request & support guys 🙏.
1 point · 2 comments
Launching BossConsole: a desktop workspace with 200+ MCP tools for coding agents
I started BossConsole as a side project in February 2025. One question kept bothering me: if a tool is available to me inside my workspace, why can’t my agent use it too?
I loved the plugin ecosystem in IDEs like IntelliJ, but wanted those capabilities to be accessible to agents. That became a big part of what I started building.
Today, sharing the BossConsole launch video.
BossConsole brings coding agents, terminals, a browser, an editor and logs into one desktop workspace. You can run Claude Code, Codex, Gemini CLI, OpenCode and other agents side by side.
The part relevant to this community is the MCP layer. BossConsole exposes workspace capabilities through 200+ MCP tools, with individual controls over which tools are available and approvals for actions. Plugins can extend the workspace and expose additional capabilities to agents.
For me, having the tools and their visible interfaces together matters. I want to follow what an agent is doing, inspect the result and take over when needed, without constantly switching applications.
I’m co-founder and CTO of Risa Labs, where we apply AI to critical problems in oncology workflows. That work keeps bringing me back to the same architectural questions: how do we give agents useful capabilities, control their access and keep extending the system as requirements change?
BossConsole is my attempt to explore those questions through a workspace I can use.
It’s open source and available for macOS, Windows and Linux.
Would love to hear how others here handle tool discovery and permissions as the number of available MCP tools grows. Do you expose a small set per task, let the agent discover tools, or leave the full set available?
Source: risa-labs-inc/BossConsole
Download: bossconsole.ai
1 point
BossConsole launch: the Compose Multiplatform desktop workspace I shared here earlier
reddit.com
Hi everyone, back with BossConsole. I shared it here earlier while looking for Compose contributors, and some of you took the time to actually look through the code and give feedback. Appreciate that, especially the comments around code structure and hardcoded styling.
Today, sharing our launch video. Quite happy to see the different parts of this project coming together.
For anyone who missed the earlier post, BossConsole is an open-source desktop workspace built using Kotlin Multiplatform and Compose Multiplatform. The desktop app runs on the JVM across macOS, Windows and Linux.
It brings coding agents, terminals, browser, editor and logs into one workspace. You can run Claude Code, Codex, Gemini CLI, OpenCode and others side by side, with each session in its own pane. Spaces remember your layout so you can return to where you left off.
The video also gives a look at the built-in Fluck Agent, visual workflows and tool approvals. There are 100+ MCP tools with individual controls over what agents can access.
One part I’m particularly interested in taking further with the Compose community is the plugin system. A tool can have its own Compose UI and ViewModel, packaged separately and loaded at runtime. I like the possibility of someone building a panel for their own workflow and bringing it into the application without changing the host.
For me, the motivation is simple: working with more agents should give us more room to explore and create. Keeping track of their sessions and moving between windows shouldn’t take over the work itself.
Still plenty to improve. Would love feedback on the UI and workflow, and contributions around Compose Desktop rendering, theming or new plugins. Happy to discuss implementation details too.
Source: risa-labs-inc/BossConsole
Download: bossconsole.ai
2 points
Launching BossConsole, an open-source desktop workspace for AI agents built with Kotlin Multiplatform
Hi everyone, excited to share BossConsole with this community. We’ve built it using Kotlin Multiplatform and Compose Multiplatform, with the desktop app running on the JVM across macOS, Windows and Linux.
Attached our launch video to give you a look at what we’ve been building.
The idea came from working with coding agents and spending too much time managing everything around them. Multiple terminals, browser windows, editors and logs, then remembering which agent was doing what. Wanted a workspace where I could keep all that work visible.
BossConsole lets you run Claude Code, Codex, Gemini CLI, OpenCode and other agents side by side, alongside their tools. Each session gets its own pane, and Spaces remember your layout.
There is also a built-in Fluck Agent, visual workflows, and 200+ MCP tools with individual access controls and action approvals.
On the Kotlin side, one part I’m particularly interested in is the plugin architecture. Tools can be built as separate Compose UI + ViewModel plugins and loaded at runtime. The terminal also lives in its own project, BossTerm.
I want someone to be able to build a tool for their own workflow and bring it into the workspace without changing the whole application. Would love to connect with others exploring similar ideas with Compose Desktop.
For me, as agents become more capable, there is more room to explore problems, try approaches and create. But we still need to follow their work and decide where to take it. That’s what I’m trying to build around.
Quite happy to finally share this launch. The project is open source, contributions are welcome, and I’d appreciate feedback from the Kotlin community on both the experience and implementation.
Source: risa-labs-inc/BossConsole
Download: bossconsole.ai
2 points · 2 comments
BossConsole update: a short demo of the Kotlin/Compose desktop workspace
Hi everyone, back with an update on BossConsole. Previously shared the architecture when we open-sourced it, then some browser benchmarks. This time, wanted to show how the workspace comes together.
Watch the one-minute demo
For anyone seeing it for the first time, BossConsole is a desktop workspace built using Kotlin Multiplatform and Compose Multiplatform, running on the JVM across macOS, Windows and Linux.
You can run Claude Code, Codex, Gemini CLI and other agents side by side, with terminals, browser, editor and logs in the same window. Spaces remember your layout so you can come back to the work without arranging everything again.
The demo also shows the built-in Fluck Agent, tool approvals and visual workflows. There are 200+ MCP tools with individual controls, and plugins to extend the workspace.
For me, the motivation is quite personal. As I work with more agents, managing sessions and following their work becomes a task itself. I want to spend more time exploring a problem, trying approaches and reviewing results, while keeping execution visible.
On the Kotlin side, the runtime plugin system is something I’m particularly interested in taking further. You can build tools as separate Compose UI + ViewModel plugins. Would love to connect with others working on extensible desktop apps and hear how you’re approaching this.
Still a lot to improve, but quite happy to share where it is today. Curious what feels useful or awkward in the demo. Happy to discuss the Kotlin/Compose implementation too.
Source: risa-labs-inc/BossConsole
Download: bossconsole.ai
2 points
Mentions
Unfair server kick from a hackathon We can't even say moderator if they are doing any mistake? Please view my request & support guys 🙏.
Launching BossConsole: a desktop workspace with 200+ MCP tools for coding agents I started BossConsole as a side project in February 2025. One question kept bothering me: if a tool is available to me inside my workspace, why can’t my agent use it too? I loved the plugin ecosystem in IDEs like IntelliJ, but wanted those capabilities to be accessible to agents. That became a big part of what I started building. Today, sharing the BossConsole launch video. BossConsole brings coding agents, terminals, a browser, an editor and logs into one desktop workspace. You can run Claude Code, Codex, Gemini CLI, OpenCode and other agents side by side. The part relevant to this community is the MCP layer. BossConsole exposes workspace capabilities through 200+ MCP tools, with individual controls over which tools are available and approvals for actions. Plugins can extend the workspace and expose additional capabilities to agents. For me, having the tools and their visible interfaces together matters. I want to follow what an agent is doing, inspect the result and take over when needed, without constantly switching applications. I’m co-founder and CTO of Risa Labs, where we apply AI to critical problems in oncology workflows. That work keeps bringing me back to the same architectural questions: how do we give agents useful capabilities, control their access and keep extending the system as requirements change? BossConsole is my attempt to explore those questions through a workspace I can use. It’s open source and available for macOS, Windows and Linux. Would love to hear how others here handle tool discovery and permissions as the number of available MCP tools grows. Do you expose a small set per task, let the agent discover tools, or leave the full set available? Source: risa-labs-inc/BossConsole Download: bossconsole.ai
BossConsole launch: the Compose Multiplatform desktop workspace I shared here earlier reddit.com Hi everyone, back with BossConsole. I shared it here earlier while looking for Compose contributors, and some of you took the time to actually look through the code and give feedback. Appreciate that, especially the comments around code structure and hardcoded styling. Today, sharing our launch video. Quite happy to see the different parts of this project coming together. For anyone who missed the earlier post, BossConsole is an open-source desktop workspace built using Kotlin Multiplatform and Compose Multiplatform. The desktop app runs on the JVM across macOS, Windows and Linux. It brings coding agents, terminals, browser, editor and logs into one workspace. You can run Claude Code, Codex, Gemini CLI, OpenCode and others side by side, with each session in its own pane. Spaces remember your layout so you can return to where you left off. The video also gives a look at the built-in Fluck Agent, visual workflows and tool approvals. There are 100+ MCP tools with individual controls over what agents can access. One part I’m particularly interested in taking further with the Compose community is the plugin system. A tool can have its own Compose UI and ViewModel, packaged separately and loaded at runtime. I like the possibility of someone building a panel for their own workflow and bringing it into the application without changing the host. For me, the motivation is simple: working with more agents should give us more room to explore and create. Keeping track of their sessions and moving between windows shouldn’t take over the work itself. Still plenty to improve. Would love feedback on the UI and workflow, and contributions around Compose Desktop rendering, theming or new plugins. Happy to discuss implementation details too. Source: risa-labs-inc/BossConsole Download: bossconsole.ai
Launching BossConsole, an open-source desktop workspace for AI agents built with Kotlin Multiplatform Hi everyone, excited to share BossConsole with this community. We’ve built it using Kotlin Multiplatform and Compose Multiplatform, with the desktop app running on the JVM across macOS, Windows and Linux. Attached our launch video to give you a look at what we’ve been building. The idea came from working with coding agents and spending too much time managing everything around them. Multiple terminals, browser windows, editors and logs, then remembering which agent was doing what. Wanted a workspace where I could keep all that work visible. BossConsole lets you run Claude Code, Codex, Gemini CLI, OpenCode and other agents side by side, alongside their tools. Each session gets its own pane, and Spaces remember your layout. There is also a built-in Fluck Agent, visual workflows, and 200+ MCP tools with individual access controls and action approvals. On the Kotlin side, one part I’m particularly interested in is the plugin architecture. Tools can be built as separate Compose UI + ViewModel plugins and loaded at runtime. The terminal also lives in its own project, BossTerm. I want someone to be able to build a tool for their own workflow and bring it into the workspace without changing the whole application. Would love to connect with others exploring similar ideas with Compose Desktop. For me, as agents become more capable, there is more room to explore problems, try approaches and create. But we still need to follow their work and decide where to take it. That’s what I’m trying to build around. Quite happy to finally share this launch. The project is open source, contributions are welcome, and I’d appreciate feedback from the Kotlin community on both the experience and implementation. Source: risa-labs-inc/BossConsole Download: bossconsole.ai
BossConsole update: a short demo of the Kotlin/Compose desktop workspace Hi everyone, back with an update on BossConsole. Previously shared the architecture when we open-sourced it, then some browser benchmarks. This time, wanted to show how the workspace comes together. Watch the one-minute demo For anyone seeing it for the first time, BossConsole is a desktop workspace built using Kotlin Multiplatform and Compose Multiplatform, running on the JVM across macOS, Windows and Linux. You can run Claude Code, Codex, Gemini CLI and other agents side by side, with terminals, browser, editor and logs in the same window. Spaces remember your layout so you can come back to the work without arranging everything again. The demo also shows the built-in Fluck Agent, tool approvals and visual workflows. There are 200+ MCP tools with individual controls, and plugins to extend the workspace. For me, the motivation is quite personal. As I work with more agents, managing sessions and following their work becomes a task itself. I want to spend more time exploring a problem, trying approaches and reviewing results, while keeping execution visible. On the Kotlin side, the runtime plugin system is something I’m particularly interested in taking further. You can build tools as separate Compose UI + ViewModel plugins. Would love to connect with others working on extensible desktop apps and hear how you’re approaching this. Still a lot to improve, but quite happy to share where it is today. Curious what feels useful or awkward in the demo. Happy to discuss the Kotlin/Compose implementation too. Source: risa-labs-inc/BossConsole Download: bossconsole.ai