repowisebacknotprop/plannotator

Architecture of backnotprop/plannotator

backnotprop/plannotator is 6,428 source files holding 60,653 symbols across 7 modules, written mainly in TypeScript, Shell, Astro. The largest module is packages, with 4,582 files, and 25 files are entry points into the dependency graph.

How plannotator fits together

Input enters through agent-specific entry points, such as apps/hook/server/cli.ts for hooks, apps/opencode-plugin/server.ts for OpenCode and apps/pi-extension/server.ts for Pi. When an agent proposes a plan or finishes work, the review app opens in the browser. The build directory packs the review, hook and inbox front ends into single HTML pages, with build/pack-app.ts supplying the review and hook builds. The packages directory holds most of the code, including packages/inbox/App.tsx for the Inbox interface and packages/server/inbox.ts for its server side. The user's annotations and comments are sent back to the agent, which acts on them. The bin directory contains the command-line entry point.

Largest modules

  • packages: 4,582 files and 882,377 lines of code
  • apps: 772 files and 141,750 lines of code
  • tests: 473 files and 113,226 lines of code
  • scripts: 77 files and 20,083 lines of code
  • build: 10 files and 663 lines of code
  • spec: 3 files and 63 lines of code
  • bin: 1 file and 19 lines of code

Languages

By file count: TypeScript 5,800 files, Shell 41 files, Astro 32 files, JavaScript 24 files, Python 14 files, Dockerfile 1 file.

Documentation

Repowise documents plannotator in 4,197 pages generated from the source, 43 of them written explanations of the repository and its modules. Module guides include:

  • packages/ai: AI Provider Sessions
  • packages/ui/utils: Agent Tool and Chat Utilities
  • packages/review-editor/utils: Annotation Display and Scope Utilities
  • apps: Apps Packages (11)
  • bin: Binary Launcher
  • apps/droid-plugin/commands: CLI Commands

More on plannotator: summary and FAQ, codebase overview, code health.

Related guide: Best dependency graph tools for monorepos