AI / Orchestration / Desktop

Kaosio

A workspace for creating and coordinating agents.

Conversations, context and automations in one workspace where agents can work together.

Original brand · conceptual composition
Context
Personal initiative
Authorship and contribution
Individual conception and execution
Current stage
In active development

01 / Kaosio

The starting point

Working across separate AI tools creates another job: moving context around, forwarding results and coordinating each step manually. The user becomes the messenger between agents.

Kaosio starts with a question: how can agents with different instructions, capabilities and responsibilities share a workspace while keeping their work visible?

02 / What I built

A workspace for creating and coordinating agents.

I built a desktop application that brings files, conversations and agents into a project context. Each agent has its own configuration, while Mesh provides a visual surface for relationships, hand-offs and ongoing work.

The same foundation supports event-driven automations and Action Nodes: deterministic actions with explicit inputs, outputs and execution boundaries. The goal is to build tools that can be combined into new workflows.

03 / Capabilities and deliverables

Capabilities and deliverables

01

Workspace context

Folders, files, conversation history, attachments and code-change inspection in the same environment.

02

Agent catalog

Create, edit, import and share agents with their own instructions, models, tools and access posture.

03

Agent Mesh

A coordination canvas with per-agent channels, delegation, consultation and results returned to the originating conversation.

04

Automations and Action Nodes

Rules triggered by events such as completed work or file changes, connected to agents and executable actions.

05

Tools and contracts

MCP integrations and structured output contracts connect tools and make results usable by subsequent steps.

06

Multiple runtimes

Agent runtimes and compatible providers are integrated with the capabilities and limitations of each path kept explicit.

04 / Decisions that shaped it

Decisions that shaped it

01

Coordination as part of the product

Agent hand-offs have identity, destinations and rules. Collaboration becomes an inspectable workflow instead of a sequence of copied messages.

02

Permissions belong to the agent

Delegation should not expand the initiating agent's authority. Access boundaries are part of the coordination architecture.

03

Creation within the tool itself

The workspace also helps author agents, skills and actions: a practical expression of building things that create things.

05 / My contribution

Individual conception and execution

KaosioBrand and visual identity

Design is part of what I build.

I also created the project's brand and visual language. Identity, interface and communication developed alongside the idea and its implementation.

  • Product conception and design
  • Brand, visual identity and interface design
  • Workspace, agent and coordination architecture
  • Interface and desktop application
  • Integrations, automations, access controls and validation

Technologies and concepts

  • TypeScript
  • React
  • Electron
  • MCP
  • AI agent runtimes

06 / Current stage

What the work made possible

An implemented environment for conversations, agent creation and coordinated work, including Mesh and automations. The product remains in active development.

Access and availability

Desktop application in development. Distribution and validation vary by platform; no public download is listed here.

Discuss this work