Machine

Isolated, observable, autonomous bots that excel at memory and self-improvement. Tools, machines and coding environments are connected via MCP.

Installation

curl -fsSL https://raw.githubusercontent.com/stagewise-io/klex/main/install.sh | sh

irm https://raw.githubusercontent.com/stagewise-io/klex/main/install.ps1 | iex

Principles

A Klex Bot has one permanent session

All incoming messages enter the same durable default session. Wherever you chat with the bot, it has the same context. Extensions can explicitly create isolated child sessions when a background-task needs separate context, tools, or model behavior.

Klex bots are mcp-native

The core agent loop is built around mcp-support. Incoming messages are sent via mcp servers that implement mcp-extension-push-notifications. Realtime calling is implemented via mcp-extension-realtime-media.

Klex bots can't touch their host computer

During runtime, the Klex Bot process only accesses data in one dedicated, isolated data-directory on its host machine. Connections to outside environments and machines are established via MCP. By implementing MCP extensions, MCP servers can wake-up a Klex Bot (mcp-extension-push-notifications) or initiate a voice- and video-call (mcp-extension-realtime-media).

Klex bots learn and self-improve (and keep their learnings organized)

After every unit of work, a Klex Bot will reflect on its actions and conversations - it will create and organize learnings as skills to do the task more efficiently the next time and remember preferences.

You can voice-call Klex Bots

Voice conversations via latest realtime models are integrated out of the box. mcp-extension-realtime-media lets you initiate a call via MCP - and swill make the bot switch to an agreed-upon realtime protocol (so far, only LiveKit is supported).

Community

• Join the Discord

License

Klex is licensed under the Apache License 2.0.