Operator client & harness
Kido CLI
Command-Line Interface
The operator’s terminal and web client for Profile conversations and modes, spanning families.
Two surfaces, three shared ports
- ConversationPort
- ChatPort
- HarnessConfigPort
Conceptual illustration. See current scope & status below.
What is Kido CLI?
Kido CLI is the operator’s client for conversations with Profiles in the terminal and on the web. Each conversation runs in a Mode. The CLI owns a harness around three ports: ConversationPort for starting and continuing conversations, ChatPort for posting and receiving Room messages, and HarnessConfigPort for rendering configuration into vendor-specific files.
What it is designed to do
- Hold conversations with enrolled Profiles through the operator’s selected harnesses.
- Use modes as presets over ports, harness policy, default adapter and output sink, rather than separate engines.
- Connect conversation, room messaging and harness configuration across product workflows; Code is one mode, not the client itself.
Illustrative use case
How it could fit into your work
An operator selects a Profile and starts a tool-free Chat conversation, or uses the code preset for a git-managed kido with a branch, merge request and Brain.
An example of the intended role, not a claim of a released workflow.