Authority beyond the prompt
The harness governs the tools an agent can use. A model's suggestion does not become permission to execute.
AI agents can sound convincing even when the work isn't done. Markhor keeps the model's claims separate from the permissions, actions, and evidence behind them.
“Explore this repository and explain what it does.”
Agents can misunderstand a repository, skip a step, or report success prematurely. Better models help, but the execution layer still needs independent controls and traceable observations.
The harness governs the tools an agent can use. A model's suggestion does not become permission to execute.
Inspect tool requests, outcomes, source observations, and Run records alongside the agent's response.
Designed around local Ollama inference and configurable provider routes, without binding execution policy to one model.
Markhor is an agent harness, not another language model. It is the layer between what an agent proposes and what the system actually does.
Point Markhor at an existing repository and describe what you want to accomplish.
Select a model and the level of tool authority appropriate for the task.
Follow model activity, inspected sources, tool outcomes, and recorded events.
Evaluate the final response against what the execution evidence actually supports.
Markhor separates model-generated responses from the tool activity behind them. When an agent says it explored a codebase, you can inspect what the harness actually observed.
Conceptual product flow, not a screenshot or a claim that every agent conclusion has been verified.
Markhor is an early alpha under active development. The current focus is controlled execution, meaningful evidence, and improving agent reliability on real software projects.
No. Markhor is a harness that connects to AI models and governs how agent tasks interact with tools, repositories, and execution records.
Yes. The alpha supports local Ollama inference and has been exercised with small and larger locally hosted models. Capabilities and performance depend on each deployment.
No. It lets you inspect what was requested, executed, and observed. Semantic correctness still requires appropriate verification and judgment.
Markhor is currently an early alpha rather than a publicly released product. Public availability and access details will be announced on this site when ready.
Different models. Different infrastructure. One independent layer for control and visibility.