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
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
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 | JWT cookie | Self-hosted / OSS |
| Cloud | Supabase Auth | JWT (Supabase managed) | CodePlans.ai hosted |
- —Email/password authentication
- —Password change with current-password verification
- —Middleware-enforced route protection
- —No session data in local storage (JWT cookie)
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 |
|---|
| MCP Server |
| Integrated AI |
| Analytics Dashboard |
| GitHub / GitLab integration |
| Linear integration |
| AI-generated changelogs |
| Asset graph visualisation |
| Billing / Subscriptions |
| OAuth providers |
| Turso cloud SQLite |