Vision
kbagent is already a strong foundation for AI agents (structured JSON output, self-documentation via context, permission model, multi-project parallelism, Claude Code plugin). But to move from being a tool for agents to a partner for agents, we need higher-level primitives.
This epic tracks features that give agents pre-assembled context instead of forcing them to build it from individual API calls.
Child issues
Also related
Design principles
- Intent over CRUD — commands should match what agents want to do, not what APIs offer
- Context pre-assembled — don't make agents correlate 5 API calls when one command can do it
- Executable suggestions — output should include runnable next-step commands, not prose
- Layered abstraction — low-level CRUD remains available, high-level commands build on top
Background
Inspired by the "agentic user experience" (AUX) discussion — headless doesn't mean brainless. The ergonomics of the agent interface matter more than API coverage.
Vision
kbagent is already a strong foundation for AI agents (structured JSON output, self-documentation via
context, permission model, multi-project parallelism, Claude Code plugin). But to move from being a tool for agents to a partner for agents, we need higher-level primitives.This epic tracks features that give agents pre-assembled context instead of forcing them to build it from individual API calls.
Child issues
kbagent diagnose— intent-based debugging (related to kbagent check: Platform observability with AI-powered investigation #74)kbagent job verify— post-execution validationkbagent pipeline trace— end-to-end data flow mappingkbagent recipe— workflow templates for multi-step taskskbagent suggest— contextual recommendationsAlso related
kbagent check/kbagent observe— platform observability with AI investigationDesign principles
Background
Inspired by the "agentic user experience" (AUX) discussion — headless doesn't mean brainless. The ergonomics of the agent interface matter more than API coverage.