Skip to content

Choose CMD, TUI, or MCP

Choose the interface by how you want to work and where the Agent should reason.

ModeInteractionAgent executor
CMDCommands, files, JSON, scriptsProject Service
TUIPersistent terminal screens and formsProject Service
External MCP with useMcpAgent: trueConnected Agent clientExternal client
External MCP with useMcpAgent: falseConnected Agent clientProject Service

CMD and TUI need llms.default plus its startup credential for service execution. The default external MCP policy uses the connected client's Agent environment and needs no project model configuration. A Service can start before either execution environment is ready.

Suggested routes

Start with installation and project initialization, then choose CMD, TUI, or MCP. The dedicated client adapter currently provided by IntLoom is Codex.

All interfaces share execution and formal data. Closing a client ends its observation; use an explicit cancel or stop operation to control work. The executor is fixed when a Run is created.

For custom processes, follow Workflow development. For embedding a trusted Node.js client, see ProjectClient.