Òtítọ́

Models generate the change. Otito proves whether it is safe to merge.

  ___ _____ ___ _____ ___
 / _ \_   _|_ _|_   _/ _ \
| | | || |  | |  | || | | |
| |_| || |  | |  | || |_| |
 \___/ |_| |___| |_| \___/

The generic agent loop (prompting, retries, tool routing, file editing) is becoming infrastructure. Frontier models already plan, search repositories, use tools, and recover from mistakes. Model vendors are packaging native harnesses with file tools and sandbox execution. Competing there is a losing bet.

What remains strategically important is the trust harness: accurate repository context, permission and sandbox boundaries, exact validation against the changed code, risk-sensitive policies, CODEOWNERS and human approval, reproducible receipts, and independent evidence the model cannot award itself. Stronger models increase that need, because teams will let them change more code with less supervision.

Òtítọ́ is that independent trust layer. It is local-first, deterministic, and model-agnostic: it discovers repositories, builds local indexes, generates task-aware context before an agent edits, scores how much a change actually touches, and gates merge readiness. It works the same way every time, with no server, no account, and no code leaving the machine. It does not compete with Codex, Claude Code, Gemini, Cursor, or future native harnesses. It integrates with them, and keeps working as models change underneath it.

Trusted agent workflow

New in v1.9.2: otito is now listed on mcpservers.org.

Request -> context -> scoped change -> exact validation -> review evidence -> human decision

Otito helps the agent understand and bound a task before editing, then gives the maintainer evidence to decide whether to trust the result. A passing local gate is never an automatic merge approval: hosted CI, GitHub review, CODEOWNERS, and the human release decision remain separate authorities.

It does not try to replace native agent harnesses, opensrc, code-structure, Daytona, or Harnss. It gives developers and coding agents a single CLI that can:

Deterministic merge gates are the differentiated core. This is the human-in-the-loop checkpoint that a model cannot grade for itself:

• score merge readiness for local changes and pull requests with one review_gate tool (gate on the CLI)
• execute a protected validation plan against the exact staged tree and retain a bounded receipt of its outcomes
• bind staged web, API, and shared-contract changes into one workspace receipt
• resolve CODEOWNERS to required reviewers and surface owner-decision warnings
• check branch-protection expectations and required checks before merge
• generate actionable PR review context from git diffs and optional GitHub comments
• continuously prove the local gate against a committed valid control and adversarial change corpus with otito eval --gate-effectiveness

Local-first context feeds the gates:

• inspect a repository
• discover and index local repositories
• maintain a local catalog and search across it
• generate task-aware context packets before an agent plans or edits
• generate AST-backed JSON-first code maps for agents
• generate a setup/validation/runtime harness for a repo
• produce Markdown or JSON reports
• estimate context-token size for generated artifacts
• run an MCP server for agent hosts with a persisted per-user index cache that never dirties an inspected repository
• expose simple agent-friendly tool metadata
• check tool availability
• generate TypeScript structure HTML through code-structure
• search dependency source through opensrc

Documentation

The published MkDocs site is a practical discovery and delivery guide:

• Home
• Executive Summary
• Context Foundation
• MCP and Agent Workflows
• Contributor Governance
• Release Readiness
• Trust-Layer Demo
• Builder-Founder Operating Loop
• Harness Thesis & Agent Experience
• Tutorials Integration (Codespaces)
• Convergence Thesis & Score
• Usage & Performance Dashboard
• Determinism Thesis & Harness Boundary
• Dual-Mode Thesis & Complementary Stack
• Prompt Determinism Thesis & Settings Trap
• Trust Harness Thesis & Commodity Loop
• Herdr Integration
• Clean Code Thesis & the Smallest Owner File
• Evaluation Method and Gate-Effectiveness Corpus
• Glossary

Read it at:

https://bashbop.github.io/otito/

Quick Start

Code maps use the TypeScript compiler for JS/TS and dedicated language extractors for Go, C#, Python, Java, Ruby, and Rust (see src/lib/code-map/ast-languages.js). Optional external tools are only needed for dependency-source lookup and HTML structure reports.

Install the published package from npm:

npm install -g @bashbop/otito
otito doctor
otito index ~/projects --discover
otito context "add a new MCP tool" --path .

You can also run a command without a global install:

npx -y @bashbop/otito doctor

For source development:

git clone https://github.com/BASHBOP/otito.git
cd otito
npm ci
npm run ci
node src/cli.js doctor

The current release is available through npm, GitHub Releases, and the MCP Registry as io.github.BASHBOP/otito.

Run Otito as the trust layer inside a Herdr agent workspace:

herdr plugin install BASHBOP/otito/integrations/herdr
herdr plugin pane open --plugin bashbop.otito --entrypoint trust-status

The Herdr plugin uses the independently installed otito CLI. Herdr owns persistent agent terminals and worktrees; Otito owns context, impact, review, and deterministic gate evidence.

otito repo . --json
otito discover ~/projects --depth 2 --json
otito index ~/projects --discover
otito catalog
otito search "events controller"
otito context "add a new MCP tool" --path .
otito impact . "add a new MCP tool" --top 12
otito ax . "add a new MCP tool"
otito map . --json
otito harness . --out .otito/harness.md
otito pr . --base origin/main --out .otito/pr-review.md
otito review . --request "add a new MCP tool" --base origin/main
otito gate . --staged --base origin/main
otito gate . --staged --run-validation
otito mcp
otito report . --out .otito/report.md
otito workspace /path/to/web /path/to/api --out .otito/workspace.md
otito workspace-gate /path/to/web /path/to/api --request "ship the product change" --out .otito/workspace-gate.md

Optional external tools:

npm install -g opensrc code-structure

Then:

otito deps zod --query parse
otito structure . --out .otito/structure.html

Usage Examples

For Codex, Claude Desktop, VS Code, Cursor, Gemini CLI, Kimi Code, Grok handoff guidance, and generic stdio client snippets, see MCP and Agent Workflows.

otito vs alternatives