What problem does it solve?
Agents working inside a Kortix session sandbox often need to act on the project's control plane — managing secrets, spawning subagent sessions, opening change requests, calling connectors — rather than just editing files, and doing that by hand through a dashboard breaks automation.
Core Features & Use Cases
- Session orchestration: Spawn, watch, and collect results from subagent sessions with commands like
kortix sessions new --json --wait and kortix sessions cp for moving deliverables between sandboxes.
- Change request workflow: Land work on
main only through kortix cr open, keeping human review in the loop for every branch merge.
- Secrets and connectors: Request secrets via human-entry links with
kortix secrets request and invoke configured connector actions server-side with kortix connectors call.
- Use Case: An agent finishes a data analysis on its branch, commits and pushes, opens a change request with
kortix cr open --title, then spawns a follow-up session with kortix sessions new --with-file data.csv to build a report from the results.
Quick Start
Ask the agent to run kortix skills get kortix-system to load the full live CLI reference, then use kortix sessions status to see every agent working on the project.