Runtime
Agentic coding environment
Keaz
An agentic coding environment built around control.
Keaz brings terminal-native agent work, editor context, permissioned changes, and reviewable sessions into one local workflow for serious repositories.
How Keaz works
The terminal is the first-class IDE surface.
Keaz starts where developers already work: the repository, shell, and editor. The runtime can read project instructions, inspect files, stream model output, run approved tools, propose edits, and preserve the session trail for later review.
- OrientLoad workspace context, instructions, git state, and visible editor metadata.
- PlanKeep the user in control before writes, commands, or broader permissions happen.
- ExecuteRun shell, file, search, MCP, and editor bridge actions through one policy layer.
- ReviewOpen diff previews, keep or revert changes, and preserve the session evidence.
Product surface
Built for the practical work around agentic coding, not only the prompt.
Workflow
Daily developer loop
Interactive CLI, TUI panes, `keaz exec`, slash commands, diagnostics, and resumable sessions.Editor bridge
Editor control
Active-file context, diagnostics, visible tabs, changed-file previews, and bridge doctor reports.Trust
Trust mechanics
Sandboxing, path grants, approval memory, protected metadata paths, and dry-run-first setup flows.Why it matters
Agentic coding tools become process runtimes the moment they touch real repos.
Keaz treats process execution, file mutation, provider routing, editor context, and state recovery as core product architecture. That makes it a stronger foundation for coding agents than a UI-only assistant.
Product portfolio
Move across the Open T Labs product portfolio.
Next step
Bring the agentic coding workflow you want to make real.
Open T Labs can walk through Keaz as a product direction, implementation reference, or scoped agentic IDE build path.