Easter Egg: /thinkback Year‑in‑Review vs /btw Bypass – Two Commands, Two Engineering Philosophies

/thinkback: Turning Code History into a Year‑in‑Review Ceremony

Implemented in dist/cli.js modules G67 and MH8. Registers as a local-jsx feature flag tengu_thinkback and is lazily loaded via dynamic import. Core constants: MARKETPLACE = "anthropics/claude-plugins-official", PLUGIN_KEY = "thinkback@<version>".

Four‑stage workflow

Installation check (RFz component) – State machine

checking → installing-marketplace → installing-plugin → enabling-plugin → ready

. If the plugin is absent, it is fetched from GitHub Marketplace and enabled automatically; UI shows only a spinner and status text.

User choice (VFz component) – First entry shows a single “Let’s go!” button. After the first run four options appear: Play animation / Edit content / Fix errors / Regenerate. This progressive disclosure reduces initial decision cost.

Skill delegation – Selecting Regenerate sends a natural‑language task prompt to the main Agent, which invokes the external thinkback skill with mode=regenerate. The skill generates a fresh year‑in‑review animation without modifying the main program.

ASCII playback (m1q function) – Produces three artifacts: year_in_review.js (data), player.js (renderer), and year_in_review.html (browser version). Playback runs in an alternate‑screen full‑screen mode and exits automatically; the HTML version can be opened in a browser.

/btw: A Bypass Query Channel That Doesn’t Interrupt the Main Flow

Defined in dist/cli.js modules Fd_ and J9q with immediate: true, so the command renders a JSX floating window directly on the REPL instead of entering the async generator loop. Usage: /btw <your question>.

The entry function records a persistent btwUseCount (to suppress repeated tip) and renders BtwDialog. Core logic resides in the GLz helper, which builds an isolated context:

async function GLz(context: ToolUseContext): Promise<BtwParams> {
  // 1. Clone messages, dropping the incomplete last assistant message
  const forkMessages = cloneMessages(removeIncompleteLastMessage(context.messages))
  // 2. Parallel fetch of system context (non‑blocking)
  const [tools, userCtx, sysCtx] = await Promise.all([
    getToolDescriptions(context.options.tools, context.options.mainLoopModel),
    getUserContext(),
    getSystemContext(),
  ])
  return {
    systemPrompt: buildSystemPrompt(tools),
    userContext: userCtx,
    systemContext: sysCtx,
    toolUseContext: context, // read‑only reference
    forkContextMessages: forkMessages, // independent copy
  }
}

Key points of GLz: forkContextMessages is a clone, so modifications never affect the main context. toolUseContext is read‑only, allowing the bypass Agent to understand the main thread without mutating it. removeIncompleteLastMessage strips messages whose stop_reason === null, preventing half‑finished assistant messages from contaminating the forked context.

The ZLz function further sanitises the message list by removing a trailing assistant message that is still streaming ( type === "assistant" && stop_reason === null). This defensive check avoids hidden bugs that appear only under load or network jitter.

UI design of BtwDialog – zero intrusion

BtwDialog

overlays the REPL as a floating JSX window because of immediate: true. The main task output continues scrolling underneath; pressing ESC closes the dialog and resumes the main flow. The persistent btwUseCount ensures the tip “this command does not interrupt the main line, ESC to close” is shown only on first use.

Comparison

Purpose : /thinkback generates a year‑in‑review ASCII animation; /btw answers an ad‑hoc query without halting the primary task.

Design philosophy : /thinkback embraces a stateless, ritualistic UI; /btw enforces context isolation for safety.

Core components : /thinkback uses RFz + VFz + Skill delegation + m1q playback; /btw relies on GLz cloning, ZLz cleaning, and BtwDialog UI.

Typical scenarios : /thinkback for personal or team retrospectives; /btw for side questions during a running task.

Engineering highlights : /thinkback updates animation logic without touching the main program; /btw’s cloned forkContextMessages prevents accidental state mutation, and ZLz’s guard blocks a class of subtle bugs.

Key engineering takeaways

Delegating generation to a Skill ( thinkback) keeps the core program stable while allowing independent evolution of the feature.

Cloning the message list ( forkContextMessages) lets a bypass Agent observe the main thread without altering it.

Removing incomplete assistant messages ( ZLz) is a defensive engineering pattern that eliminates hidden bugs caused by streaming interruptions.

Persisting a usage counter ( btwUseCount) to show a tip only once respects the user’s learning curve.