Agent profiles
Planned
An Agent Profile will describe how an optional Katra agent operates. The profile is configuration; Katra Agent Harness is the runtime; a prepared Workspace is where the work happens.
Planned profile fields
Section titled “Planned profile fields”- Model and provider
- System instructions and role
- Memory implementation and scope
- Skills and skill libraries
- MCP servers and tools
- Working rules
- Workflow-specific inputs
- Environment requirements
Profiles must be versioned and must not contain plaintext secrets.
Execution boundary
Section titled “Execution boundary”Katra Server will select the workflow step, prepare an authorized workspace, attach the profile, and start or contact Katra Agent Harness. The harness will perform the assigned step and report progress, questions, results, failures, cancellation, timeout, and reconnect state back to the Server.
The Server owns workflow order. Agents do not grant themselves tools, credentials, filesystem scope, network reachability, or later steps.
First proof
Section titled “First proof”The first bounded proof is planned around one Katra-managed repository, one Workspace, two Agent Profiles, two sequential agent steps, and one human approval. It must complete while all Clients are disconnected and leave reproducible authorized evidence.
Current status
Section titled “Current status”The Agents interface is visual scaffolding. Agent Profile persistence, Katra-owned Git, workspace preparation, and authenticated harness execution are not yet available.