Roadmap Product site

Project

Feature roadmap

Where Red Pen is going - what landed recently, what is queued next across every surface and the Hub, and the exploratory ideas that are further out and less certain.

A direction, not a contract This roadmap describes intent and sequence, not dated promises. Items move, get reordered, merge, or get dropped as the work and priorities change. There are no release dates here on purpose. The one firm commitment is the one on every page: the core stays free, local-first, and dev-only, and nothing already free moves behind the paywall. For what actually ships today, see each surface's own page.

How to read this

Red Pen is a family of five surfaces (WordPress, Express, the static drop-in, Ableton Live, and the Blender add-on) plus the Red Pen Hub. The surfaces share one note model but evolve on independent version numbers - they are at very different maturity levels, so the project tracks capabilities across surfaces rather than forcing version numbers to line up. WordPress is the flagship and sets the feature bar; whichever surface is in active feature-development at a given moment is the "lead" that a new capability is built in first, after which the others follow. The colour of each band below signals its state:

Recently shipped

The most recent work, newest first. These are live in the versions documented on the surface pages.

Offline license gate - PRO is sellable wp v0.22.0 + hub v0.6.0

The last step before PRO can be sold, and it holds the credo line: PRO unlocks with an offline-signed license key the buyer pastes in, verified locally against a public key embedded in the app - no server, no phone-home, no expiry, no revocation, so a key works forever. The same key unlocks both surfaces: it turns on the plugin's white-label report branding, and it lifts the Hub's free cap. Unlicensed, the Hub still works but aggregates up to three projects - a real try-before-buy; a key unlocks unlimited. Keys are minted offline by a signer the author keeps private; the shipped public key can only verify a key, never mint one.

WordPress - white-label client report v0.21.0

The freelancer's deliverable: a clean, printable report of a site's notes grouped by status - open items and what has been resolved - with summary counts, type and severity, the page each note sits on, screenshots, and resolve dates. Generate it from the panel under Tools and use the browser's Print / Save as PDF to hand it to a client. The plain report is free (export is never gated); the branded layer is PRO - your logo, an accent colour, a custom title, and hiding the Red Pen credit, so the report goes out as your own deliverable. It is also the first PRO gate on the flagship, via a no-phone-home seam; the offline-signed license key that drives it shipped in v0.22.0 (see the license-gate entry above). See the WordPress page.

Hub - durable, two-way write-back for connected sources v0.5.9 + v0.5.11

The last gap in write-back is closed. Resolving, reopening, or starting a note on the board for a connected / push source used to be local-only and got overwritten on the next push. Now it is merged on ingest so it survives future pushes (v0.5.9) and handed back to the origin site so the source updates locally too (v0.5.11). WordPress pull sources were always two-way over REST. The board is a real control surface across every surface now. On the site side, the static drop-in reads these hand-backs and applies them locally (v0.0.8). See the Hub page.

Hub - board QoL, accessibility, and security batch v0.5.5 - v0.5.11

A wide polish pass on the board. The "When" column was split into Created and Resolved and "Where" renamed Location; each row gained a byline (author / assignee / reply count), the resolver's name on resolved notes, and a severity marker when present. Saved named views plus persistence of the active tab, sort, and filters across reloads. A CSV export alongside the Markdown one. A Start control that moves an open note to in-progress, making the three-state workflow fully reachable from the board. An accessibility pass (keyboard-operable aria-sort headers, announced tabs, dialog-role focus-trapped modals with Esc, a real light/dark switch). And a documented security posture - loopback-only bind, a DNS-rebinding Host guard, constant-time token checks, bounded re-validated outbound redirects, and a 0600 credential file. See the Hub page.

WordPress - severity field v0.20.0

Notes gained an optional Severity (Blocker / Critical / Major / Minor / Trivial) - the impact axis, distinct from priority's scheduling axis. Set it under "More" next to Priority; it is dev-only (client reviewers never see it) and shows on the note, in the CSV export, and on the Hub board. WordPress authors it today; the shared model carries it for other surfaces to adopt later. See Severities.

WordPress - every note reaches the Hub v0.19.0

The plugin's REST /notes endpoint now accepts ?scope=all, so the Hub can pull every note on the site - page- and post-attached notes were previously missing from the combined board, which only saw site-wide (target=0) notes. Notes also expose an ISO createdAt and, once resolved, resolvedAt + resolvedBy, which is what feeds the Hub's Created and Resolved columns and the resolver byline. See the WordPress page.

WordPress - client reviewer link v0.13.0

The first build from the "client feedback and handoff" theme, and the audit's most-requested capability. A non-technical client can now leave pinned notes on a WordPress site through a tokenized, shareable link - no login or account - in a restricted reviewer mode that cannot resolve, edit, delete, assign, or reach the admin repository. Generate and revoke links from a panel under Tools; reviewer feedback is badged "Client" and filterable in the repository. Free core, with the security boundary enforced on the server and a per-visitor rate limit plus instant revoke for abuse control. See the WordPress page.

Red Pen Hub - refocus on tracking v0.5.0

The Hub's old "Agent Dispatch" feature - which let you select notes and generate a paste-ready LLM work-order - was deliberately removed. Assembling and handing out prompts for language models is not the Hub's job; the Hub is a note tracker. Removing it cut a large amount of surface area (the selection mode, the batch-prompt builder, and a git "safety gate" modal) and refocused the app on what it is for. Kept: manual write-back, the markdown export, and a passive read-only git clean/dirty indicator. This item appears here only so the record is clear - it is a removal, and it is not coming back.

Red Pen Hub - two-way write-back v0.4.0

The Hub stopped being read-only. A per-row Resolve / Reopen control on the board now writes the status change back to the note's real source - editing a file store, flipping a connected store, or posting to the WordPress plugin's status route with an Application Password. This is the feature that turned the Hub from a viewer into a control surface. See the Hub page for the durability caveats around connected (push) stores.

Express middleware - notes UX parity v0.2.0

The "daily-use polish" milestone: an add-reply UI with thread rendering in the overlay; editing a note after adding it (body, type, priority, and re-pinning or clearing the anchor); Open / Resolved tabs with live counts; error toasts on failed saves; persistent add-form preferences; and an undo toast when resolving. Details on the Express page.

Ableton Live - external-file storage fix prototype

Clarified and fixed how the Live prototype persists: notes are written to an external notes.json file, never inside the .als project, with a home-directory fallback for development mode. This unblocked the paused prototype. The surface remains paused pending the Live SDK, as described on the Ableton page.

Static drop-in - Connect to Hub v0.0.2

The client-only drop-in gained a "Connect to Hub" panel: open the All-notes board, paste the Hub URL and shared token, and the browser-local notes push to the Red Pen Hub. This is what lets a purely static site appear on the aggregation board.

The next big theme: client feedback and handoff

A recent round of buyer-perspective review made one thing clear. Red Pen is excellent at organizing the developer's own notes, but the highest-value requests are all about a second person entering the loop - a client leaving feedback, a teammate sharing a board, a client receiving a finished report. That is where the next wave of work points. The guiding line is deliberately simple:

The line The second person gets in for free. The second person getting organized - across many projects, with identity, or with your branding - is where PRO begins. Collecting feedback is always free; managing it at scale is the paid extra.

Planned - free core

  • Review-snapshot handoff Free core - export a self-contained review bundle a collaborator opens, adds notes to, and sends back, like a merge. Pure local-first, no server - the way to bring a second person into a review on any surface.
  • Anchor durability Free core - pins that survive a re-render, a theme change, or a responsive reflow, via a stable-attribute and text-content fallback. Quality work that protects the core promise of pinning to the thing itself.
  • Text-range anchoring Free core - pin a note to a sentence, not just an element, so copy and content can be reviewed as precisely as layout.
  • Markdown export on every surface Free core - bringing the markdown digest down from the Hub to all surfaces. Export stays free, everywhere.
  • One free export-to-issue path Free core - send a note straight to a GitHub issue, so notes flow out to where the work actually happens.

Planned - PRO

Cross-cutting: assignees and automated work

Treat Claude and other agents as assignable users decided, pinned

Another cross-cutting theme, alongside the client-feedback work above. A note should be assignable to a person or to an AI agent, so the board can tell manual work apart from automated work at a glance. This is decided as a direction but currently pinned (intentionally parked) because the WordPress surface already has the assignee and agent model fully built - so the work is about extending it, not inventing it.

The plan, when it is picked back up:

  • Adopt the existing WordPress assignee/agent model rather than design a new one.
  • Make assigning settable from the Hub by writing back to the source, the same way Resolve / Reopen already works.
  • Bring the assignee field to the other surfaces (Express, static, Ableton) after the Hub, since they do not have it yet.

Red Pen Hub

Express middleware

Express is the surface in active feature-development, marching toward v1.0 (declared parity with WordPress) and an npm publish. The sequence after the shipped v0.2.0:

Static drop-in

Ableton Live

Resume after the SDK reaches general availability paused

The Live extension is a working prototype, paused because the Ableton Live Extensions SDK is still in beta and not publicly shippable. When the SDK reaches general availability, the planned work is a locator / cue-point layer (mirroring a note's captured anchor as a real Live locator) and per-Live-Set scoping (so notes are organized by project rather than one global store). Until then it is maintained as a personal prototype. See the Ableton page for the current state and known limitations.

Later and exploratory

Not committed Everything in this section is an idea under consideration, not planned work. It is recorded so the thinking is not lost, but none of it is scheduled, and some of it may never be built.

An event and integration system

A possible future direction for the Hub: an event-driven layer where the application emits business events (a note created, a status changed, a project updated) and optional, independently enabled integrations subscribe to them - without the core ever containing platform-specific logic. The guiding principles would be self-hosted first, no dependency on SaaS automation platforms, and events that describe what happened rather than dictate an action.

  • Phase 1 - one-way, application to external. Push activity outward: append to a Markdown vault (Obsidian, Logseq, plain folders), post to Discord or Slack, or fire generic outbound webhooks. The Markdown-vault target is the most interesting - turning notes and activity into a durable, human-readable knowledge archive that outlives the app.
  • Phase 2 - bidirectional. Read the other way too: create a task from a Markdown checkbox, detect completed items in vault files, and synchronize status changes back. Considerably more involved, and firmly in the "maybe someday" bucket.

A generic outbound webhook system would underpin most of this - exposing internal events to any external service without a dedicated integration module for each one.

Monetization direction

For completeness, since people ask how a free tool sustains itself. None of this changes the free core. The principle is the one above: collecting feedback is free; managing it at scale is the paid extra.

Previous← Red Pen Hub