⌖ Anchor

A digital sticky note & cross-session todo checkpoint docked below your Pi editor — automatically catches unfinished todo lists when you close the terminal, sticks quick notes in 0ms (pin: ...), and teleports back to the original session (/back).

English | 日本語 | 简体中文

pi install npm:pi-anchor

  ┌─ [aboveEditor stays 100% free for pi-lingual and other HUD widgets] ────────────┐
╭─┴─ Pi Editor ────────────────────────────────────────────────────────────────────╮
│ ❯ pin: Refactor auth: 1. Extract interface 2. HttpOnly cookie 3. Unit tests      │
╰─┬────────────────────────────────────────────────────────────────────────────────╯
  ├─► ⌖ #1 [■□□□ 1/3] Refactor auth (app · auth.ts ↪)                [Alt+A fold]
  │   ├─ ✓ 1. Extract auth interface (strikethrough)
  │   ├─ ◐ 2. HttpOnly cookie (editing auth.ts)
  │   ├─ ○ 3. Unit tests ⛓ #2
  │   └─ 📌 #2 Double-check gateway timeout fallback (3h ago)
  └─► (Folded via Alt+A): ⌖ #1 [■□□□ 1/3] Refactor auth ▸ HttpOnly cookie (auth.ts ↪)

Core Value

Late at night, mid-way through fixing a bug, you spot a second issue in src/auth.ts or need to pause a multi-step refactor until tomorrow. Standard ways of recording that note create immediate friction:

1. Terminal Exit Wipes Working Memory: Closing the terminal or running /new clears the agent's context. Yesterday's unfinished steps and the conversation history behind them vanish.
2. TODO.md Pollutes Git & Burns Context Tokens: Tracking personal reminders inside repository markdown files dirties git status and re-injects stale checklists into the system prompt on every turn.
3. Splash Banners Vanish When You Start Typing: Traditional startup widgets disappear on the first message. For the rest of a two-hour session, your notes are hidden unless you manually run a slash command.

Anchor acts like a physical sticky note and auto-save checkpoint stuck to the bottom bezel of your Pi editor:

• Auto-Todo Bridge (todo ➔ Cross-Session Checkpoint): Standard todo tools (@juicesharp/rpiv-todo and built-in todo) live only inside a single conversation with zero disk writes — closing the terminal or running /new wipes unfinished tasks. Anchor automatically mirrors unfinished todo snapshots to disk ([■■□□ 2/5]) and auto-clears them the moment all steps reach completed.
• Persistent Below-Editor Strip (belowEditor): Docks a single-line note strip directly beneath your input box. It stays in view while you code, leaves aboveEditor untouched for extensions like pi-lingual and rpiv-todo, and collapses to 0 lines when empty.
• 0ms Human-First Capture (pin: ...): Type pin: Check token expiry (or /pin ...) straight into the editor. An input hook intercepts the text in 0.00ms without calling the language model or spending tokens.
• Session Teleport (/back & ↪ Jump to session): Every note and auto-checkpoint bookmarks the exact .jsonl session file where work happened. Run /back (or select ↪ Jump to session in /anchor) to switch Pi straight back to that conversation.

How It Works

Features & Engineering Answers

1. Will the sticky strip collide with pi-lingual or overflow narrow split panes?

Anchor mounts its widget with { placement: "belowEditor" }. Extensions that render translation cards or diagnostics above the input box (aboveEditor) never overlap with Anchor.
On narrow terminal splits (such as 50-column tmux panes), the strip measures visual column widths using Unicode East Asian Width rules (CJK/emoji = 2 cells, ASCII = 1 cell) and dynamically folds multiple notes into ⌖ 3: #1 [■■□□ 2/4] Refactor… +2 while stripping unclosed brackets before ellipses.

2. Does keeping sticky notes cost tokens on every turn?

Turn 2+ consumes 0 system prompt tokens.
Anchor injects a compact summary of active notes only on Turn 1 of a cold session. From Turn 2 onwards, the system prompt hook returns nothing. When the agent reads or edits a file that matches a note's path or glob (src/auth/*.ts), Anchor appends a single syntax-safe comment line (// ⌖ Note #1: ...) to that tool result, while returning null for .json, .env, lockfiles, and binaries.

3. What happens to old notes or accidental git commit matches?

• 7-Day Quiet Mode (Zero Silent Deletion): Notes untouched for more than 7 days transition to sleeping (quiet). They stop appearing in Turn-1 prompts for unrelated workspaces, remain 100% visible in /anchor, and wake up automatically when you open their target project.
• Stop-Word Filtered Commit Matching & 1-Tap Undo: Commit matching strips generic words (fix, feat, chore, bug, update) so a commit like fix: typo in bug template never tears off a note titled fix bug in login. If you ever tear off a note by mistake, /anchor undo pops the last entry from archive.jsonl right back onto your strip.
• Bracketed Ratio Parsing: Progress ratios require explicit brackets ([2/4] or (5/30)), ensuring calendar dates in note titles (like Before 10/12 release) are never mistaken for progress bars.

4. Storage Topology & Cross-Process Lock Safety

All state lives in ~/.anchor/ outside your git repository:

~/.anchor/
├── state.json      # Active and quiet sticky notes (< 2KB, atomic temp-file + rename)
├── state.lock      # Cross-process exclusive lock (fs.openSync 'wx' + dead-PID reclamation)
└── archive.jsonl   # Append-only history of torn-off notes (powers /anchor undo)

Commands

Author's Note

Anchor started because I hated watching TODO.md files rot inside my git repositories, yet closing my terminal at night always meant losing track of what I still needed to fix the next morning.

In its early versions, I over-engineered the solution. By v0.3, Anchor had grown into a 10-file miniature project manager with four cognitive quadrants (Today, Upcoming, Habits, Backlog), [P0] priority tags, daily recurring habit trackers, pre-flight shell test runners on startup, and a graveyard eviction state machine. Ironically, the more features it gained, the less I wanted to use it. Worse, its startup banner disappeared the moment I typed my first message, hiding my notes for the rest of the coding session.

In v0.4 and v0.5, I threw away 60% of the codebase and rebuilt Anchor around four files (types.ts, store.ts, tui.ts, extension.ts) as a simple digital sticky note:

1. Dock the 1-line note strip below the editor (belowEditor) so it stays in sight while coding and never fights with pi-lingual above the editor.
2. Let human hands stick a note in 0ms by typing pin: ... without waiting on a model call.
3. Add a 4-cell progress bar ([■■□□ 2/4]) for multi-step refactors and bookmark the session file (↪) so clicking a note teleports you back to the exact conversation where the work started.

npm run typecheck  # Strict tsc --noEmit check (0 errors)
npm test           # Native Node test runner (15/15 passing)
npm run build      # Dual ESM/CJS compilation via tsup + declaration emit

Ecosystem: Pi Terminal Suite

Each extension occupies a distinct terminal slot (aboveEditor, belowEditor, status-only footer, and runtime tool hooks) so all four run together with zero widget overlap:

License

MIT © Jason Song