Skip to content
Developer toolsNew techTop 11% of today's analysed ideas

Plan State Persistence Layer for Claude Code Re-Runs

Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.

Original post

What to build

A lightweight CLI tool or VS Code extension that wraps Claude Code sessions with a plan-step persistence layer — tracking which steps have been executed, storing state to a local JSON or SQLite file, and skipping or flagging already-completed steps on re-runs. Built for solo developers and small teams running multi-step agentic workflows with Claude Code who lose progress when sessions restart.

Claude Code has no built-in mechanism to persist plan state or enforce idempotency across session restarts, so multi-step agentic workflows silently re-execute completed steps or lose progress entirely. A thin persistence layer sitting between the developer and Claude Code can solve this with minimal overhead.

Demand

Solo developers and small teams actively using Claude Code for complex, multi-step coding tasks are running into this repeatedly — the problem is live and unresolved right now, before Anthropic ships a native fix. The timing window is narrow but real.

  • Product HuntSocial post

    Groundwork listed on Product Hunt with the pitch 'Claude Code plans that re-runs never overwrite' — indicating at least one team has shipped a product targeting this exact gap, with public discussion on the platform.

  • Anthropic Claude Code DocumentationReference

    Current public Claude Code documentation contains no mention of native plan-step persistence or idempotency guarantees across sessions, confirming the gap is unaddressed at the platform level.

  • Agentic AI Workflow PatternsBackground

    Checkpointing and idempotency are well-established requirements in distributed systems and automation pipelines; the same need is now surfacing in LLM-based coding agents as workflows grow longer and more complex.

  • Signal AnalysisAnalysis

    Internal analysis identifies duplicated work and lost progress on session restart as a consistent pain point for Claude Code users running multi-step agentic workflows, with no native mitigation currently available.

Stack

  • Claude Code SDK / CLI hooks
  • SQLite (via better-sqlite3) for local state storage
  • Node.js or Python CLI (Commander.js / Click)
  • JSON schema for plan-step definitions
  • VS Code Extension API (optional GUI layer)
  • GitHub Actions (for CI/CD-integrated idempotent runs)

Solo + AI difficulty

The core persistence and deduplication logic is straightforward — a few hundred lines wrapping Claude Code invocations with read/write to a local SQLite file. The hard part is reliably fingerprinting non-deterministic plan steps so deduplication doesn't false-positive or miss duplicates. Realistic MVP in 1–2 weekends of focused AI-assisted coding; a production-ready version with edge-case handling is a 2–4 week project.

Entry threshold
Build a CLI wrapper or VS Code extension that intercepts Claude Code plan execution, logs completed steps to a local file or SQLite, and skips already-done actions. Buildable in a weekend with AI assistance; no special licenses needed.
Window
2-4 months

Where to find first users

  • r/ClaudeAI and r/LocalLLaMA — active communities of Claude Code power users who hit this problem directly
  • Product Hunt launch targeting the AI developer tools category
  • Anthropic developer Discord and community forums
  • Hacker News 'Show HN' post with a concrete before/after demo of re-run protection

Competitors

  • Groundwork

Counter-signals & risks

  • Anthropic may natively build plan persistence and idempotency features directly into Claude Code, eliminating the third-party opportunity before it can be monetized.

  • The target user segment — solo developers and small teams — may be too cost-sensitive to pay for a standalone persistence layer, defaulting instead to ad hoc workarounds like manual step logs or git commits.

  • Implementing a generic idempotency layer across diverse agentic workflows is technically tricky: plan steps are often non-deterministic and context-dependent, making reliable deduplication harder than it looks.

Original title: Groundwork

  • Developer tools#4

    MCP Connector Library for AI Coding Agents

    Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.

    Demand
    7/10
    est.
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Product Hunt
    22 competitors
  • Developer tools#8

    Developer Context Save and Restore Tool as Micro-SaaS

    Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
  • Developer tools#2

    Embed private on-device transcription in any web app

    Build micro-SaaS products or browser-based tools that embed this 15MB on-device transcription model (Starbright) for privacy-first use cases: meeting note-takers, voice journal apps, offline voice search for small websites, accessibility widgets, or no-server dictation tools. The key selling point is zero server cost and full privacy since audio never leaves the device. Target indie developers, privacy-focused app builders, and small business website owners who cannot afford cloud ASR APIs.

    Demand
    1/10
    measured
    Buildability
    9/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
Plan State Persistence Layer for Claude Code Re-Runs — Nichr