Repository navigation
AgentDoctor 2.0.0
[2.0.0] — 2026-09-21
AgentDoctor 2.0 expands the product from Safety + Project Brain into codebase
intelligence for developers, agents, and engineering teams — while preserving
Safety CLI behavior and Brain MCP tool names.
Canonical docs: docs/2.0/. Readiness:
docs/2.0/overview/readiness-matrix.md.
Limitations: docs/2.0/overview/known-limitations.md.
Added
- Shared contracts layer (
CONTRACTS_VERSION) unifying findings / graph /
knowledge / policy shapes. - Repository Brain productization:
init, proposal artifacts,brain review/
brain proposals/ product snapshots (proposals never auto-approved). - TypeScript/JavaScript AST intelligence graph (
graph) with regex fallback. - Git engineering intelligence (
health) with per-metric method disclosure. - C4-style architecture views (
c4) labeled inferred/proposed. - Impact surfaces:
impact,test-impact,refactor-impact. - Governed knowledge store with abstention (
knowledge,knowledge-create,
knowledge-approve). - Policy packs + AgentDoctor-controlled enforcement runner (
enforce) distinct
from evaluate-only firewall. - Combined MCP server (
agentdoctor mcp) exposing Brain tools plus
intelligence tools without renamingbrain_*. - Dashboard
/api/v2/*endpoints (graph, health, c4, knowledge,
projects/workspaces stubs). - Local-dev team authentication (
team-register,team-login) — not enterprise SSO. - Ops health via
doctor --json. - Security hardening: MCP/dashboard path-safety, symlink skip in AST walk,
secret redaction on exports/API samples. - Documentation tree:
docs/2.0/(overview, guides, reports, audits, release). - Additional 2.0 platform / Safety surfaces landed with this release train:
evaluate-only Action Policy Evaluator (platform policy-check, alias
firewall-check), session audit, provenance, context-security, architecture
drift, time-machine, token planner, readiness scorecard, multi-format reports,
Copilot / Windsurf / Gemini CLI / Aider adapters, Project Brain CLI
(brain init|status|inspect|rebuild|history|search|export|import),
changes,context-health,secrets, Safe Fix 2.0 backup/undo, named
baselines, monorepopackages, localpr-review, loopbackdashboard,
plugins, optionallocal-ai.
Security
- Path-traversal hardening for MCP
dependency_lookupand dashboard hostile URLs. - Evaluate-only policy evaluation remains explicit (
executionResult: "not-executed"). blocked-by-enforcementonly on the AgentDoctor-controlled runner block path.- Loopback dashboard default retained; non-loopback requires explicit opt-in.
- Safe Fix target hardening: refuse symlink write-through, symlink ancestors,
directory targets, and non-allowlisted paths.
Compatibility
- Safety
scan/fix/verifyworkflows and exit codes preserved. - Brain MCP tool names preserved (
brain_overview, …,brain_snapshot). - Additive CLI commands only; no intentional removal of 1.x public surfaces.
- Platform evaluate-only firewall behavior preserved.
Known limitations (at release)
- AST analysis is TypeScript/JavaScript-focused; other languages unsupported for
deep graph analysis. - Test-impact is heuristic/graph-based (no coverage-file oracle).
- C4 views are inferred, not approved architecture truth.
- No IDE interception of third-party agents.
- Local-dev team auth is not SSO.
- SQLite/Postgres/vector backends are not production-complete.
- See README limitations and
docs/2.0/overview/known-limitations.md.
Migration notes
- Upgrading from 1.1.x: existing
.agentdoctorSafety/Brain data remains valid. - New directories may appear under
.agentdoctor/repository-brain/,
.agentdoctor/knowledge/,.agentdoctor/team/,.agentdoctor/platform/. - Treat
initoutputs as proposed until reviewed. - Prefer
agentdoctor mcpfor combined tools;brain-mcpremains for Brain-only clients. - Full guide: docs/2.0/guides/migration.md.
Notes
- Readiness matrix classifications remain honest; many 2.0 surfaces are
implemented but partially validated. No blanket 5/5 claims. - Multi-writer Safe Fix is still not fully atomic across targets after preflight.
- Vitest 3 → 4/5 major upgrade remains deferred (dev-only moderate advisory).
- Do not auto-publish from CI agents. Tag/publish require a separate human step.