Features
What CodePlans does today — and what's coming.
Core planning
Planning primitives
Product & Asset Management
Define the shape of your system before you plan changes to it. Products group related assets — apps, services, libraries, datastores, and platforms. Assets carry health scores, status, tags, and dependency relationships. This shared vocabulary lets plans reference actual components, not abstract tickets.
- —Create and manage multiple products
- —Type-classified assets: app, service, library, datastore, platform
- —Asset health and status tracking
- —Dependency modelling between assets
Code Plans
A Code Plan is the primary unit of coordinated work. It targets a product and optionally specific assets, groups tasks, and carries scheduling and classification metadata.
- —Change types: Refactor, New Feature, Improvement, Bug Fix
- —Status lifecycle: Draft → Active → Completed / Cancelled
- —Schedule attributes: start date, end date, deadline
- —Tags, assignee lists, and progress tracking
Task Management
Tasks live inside Code Plans and represent individual units of work. They track status, priority, estimated effort, and assignee.
- —Status: Not Started → In Progress → Done
- —Priority levels: Low, Medium, High, Critical
- —Effort estimates (hours)
- —Tag-based filtering
Architecture intelligence
A living model of your system
Asset Atlas
A live system map drawn from your inventory — products as columns, dependency edges between assets, and lenses that recolor the map by health, debt, or delivery activity. Hover any asset to see its blast radius. Grid and sortable table views sit beside it. Derived, not drawn: it cannot rot, because it is a projection of data you already maintain.
- —Map, grid, and sortable table views
- —Health / debt / activity lenses
- —Dependency edges: depends on, integrates with, aggregates
- —Blast-radius hover — what a change touches, before you plan it
Asset Record
A capabilities register per asset, built only from delivered work. Each claim carries its lineage back to the work item, plan, and release that shipped it; derived known-issues and debt sections come along for free. Removals become tombstones, never silence.
- —Capabilities graduated from resolved work items
- —Delivery lineage on every claim
- —Derived known-issues and debt sections
- —Tombstoned removals — the record never goes quietly stale
Releases & Versions
Group the plans that ship together — a version of one asset or a coordinated multi-asset revision. Stamp per-asset versions and get release notes derived from the work items delivered, with a clear ship lifecycle.
- —Delivery grouping above code plans
- —Per-asset version stamps
- —Release notes derived from delivered work items
- —Plan-side release picker
Asset History & Design Log
Every asset carries a version-structured timeline: releases shipped, plans delivered, debt movement — all projected from existing data. Alongside it, a curated design log of notes authored by your team or your coding agents, each attributed.
- —Version ladder and derived history timeline
- —Design notes — user- and agent-authored, attributed
- —Debt movement tracked over time
AI Drafting
Feature-flagged and off unless you provide an Anthropic API key. CodePlans drafts release notes from delivered work and design notes from completed plans — always landing in an editor, never auto-published. The app never requires it.
- —Release notes drafted from delivered work items
- —Design notes drafted from completed plans
- —Always lands in an editor — humans decide
- —Gated by ANTHROPIC_API_KEY and AI_ENABLED
Team & collaboration
Working together
Organisation Accounts
Teams can operate under a shared organisation with centralised billing and member management.
- —Role hierarchy: Owner → Admin → Member
- —Invite workflow with email-based onboarding
- —Shared access to products and plans
- —Organisation-level settings
Individual Accounts
Individual users can collaborate on products via product-level invitations, without requiring a full organisation setup. Accounts can be converted to organisation accounts at any time.
- —Product-level invitations
- —Convert to organisation account at any time
- —Collaborate without enterprise overhead
Integrations & agents
Live today — in OSS and hosted alike
MCP Server
CodePlans runs a full MCP server exposing 41 tools over Streamable HTTP with API-key auth and read/write scopes. Agents read the map, file work items, model products and dependencies, log session work, record design notes, manage releases, and graduate capabilities into the asset record — with connection snippets built into the app.
- —41 tools over Streamable HTTP, read/write-scoped API keys
- —Claude Code, Cursor, Codex, GitHub Copilot, and Antigravity
- —/codeplans-capture builds the model from your docs folder
- —/codeplans-log records each coding session's work
Tracker Integrations
Mirror work items from five trackers with strict provenance — tracker-owned fields stay read-only, your annotations stay yours. PR auto-linking updates per-asset delivery status, and plan completion writes a comment back. All of it works in the OSS self-hosted build.
- —GitHub, GitLab, Jira, Asana, and Linear
- —Pull-only mirroring with strict provenance
- —PR auto-linking updates per-asset delivery status
- —Included in the OSS build — nothing is hosted-only
Work Items & Tech Debt
Work items are the demand side — features, bugs, UX issues, and tech debt — linked many-to-many to the plans that address them. Open tech-debt items roll up into a severity-weighted debt score per asset, deterministically. No AI required.
- —Types: feature, bug, enhancement, ux, tech_debt
- —Severity-weighted tech-debt score per asset
- —Dependency mapping with plan impact analysis
- —Spec-linked work — markdown specs rendered in-app
Authentication & security
Two authentication modes
Selected entirely by environment configuration — no code changes required to switch between deployment modes.
| Mode | Provider | Session Strategy | Use Case |
|---|---|---|---|
| Local | Auth.js credentials | Session cookie | Self-hosted / OSS |
| Cloud | Supabase Auth | JWT (Supabase managed) | CodePlans.ai hosted |
- —Email/password authentication (bcrypt-hashed) with session cookies
- —Closed, invite-only, or open registration modes with email invitations
- —Integration tokens encrypted at rest (AES-256-GCM)
- —Password change with current-password verification
- —Middleware-enforced route protection
Infrastructure & deployment
Pluggable data backends
CodePlans v0.2.0 introduced a full adapter pattern separating the auth and database layers from application code. Switching between deployment modes requires only environment variable changes — no code modifications.
| Backend | Auth | Database | Suitable for |
|---|---|---|---|
| Local / OSS | Auth.js | SQLite (libsql) | Self-hosted, small teams, dev |
| Cloud | Supabase Auth | PostgreSQL (Supabase) | CodePlans.ai, larger teams |
Self-hosting requirements (SQLite mode)
- —A single Node.js process (Next.js server)
- —SQLite file on a local or mounted volume
- —No external database, no cloud account required
- —Suitable for a VPS, Docker container, or home server
Feature flags
A built-in feature flag system controls visibility of in-development features. Flags operate at four levels: Production, Public Beta, Private Beta, and Alpha. Users can be granted elevated access for early feature testing.
On the roadmap
Planned features
Not yet available, but actively planned. See the full roadmap →
| Feature |
|---|
| Round-trip engineering |
| Layers & model boundaries in the Atlas |
| AI estimation & insights |
| Scheduled sync + webhooks |
| Hosted multi-org & billing |
| Analytics dashboard |
| OAuth providers |