nanostack

Your AI agent writes code. Nanostack makes sure it ships work you can trust.

Local delivery workflow harness for AI coding agents.

Scope, plan, build, review, security, QA, ship. Every step leaves evidence you can read, in plain files on your disk. Use the default sprint, or build your own workflow stack on top.

Open source. Plain text skills. Local artifacts. Verified adapters. No Nanostack cloud.

What is it · Install · The Sprint · Visual artifacts · Extend · Release notes · Español

Inspired by gstack from Garry Tan. Nanostack gives your agent the working method of a small product team: it questions the scope, plans, reviews the code, audits security, tests, and ships, leaving a paper trail you can inspect at every step. Everything is plain text and local scripts under Apache 2.0, so you can read every rule your agent follows. No Nanostack cloud, no daemon, no app runtime.

Verified adapters today: Claude Code, Cursor, OpenAI Codex, OpenCode, and Gemini CLI. The skill files are plain text, so other agents may load them, but only those five have a verified adapter and capability declaration in adapters/.

What changed in the latest release (custom workflow stacks, visual artifacts, stronger safety contracts): see RELEASE_NOTES.md.

See it work

You:    I need to add notifications to my app. Users keep missing
        replies on their posts.
You:    /think

Agent:  Before we build anything, how are users coping today?

You:    They open the app 3-4 times a day just to check. Sometimes
        they miss replies for hours. People are frustrated.

Agent:  I'm going to push back on "notifications." You said users open
        the app 3-4 times a day. That's high engagement. They already
        come back. The problem isn't that they can't be reached. The
        problem is that when they arrive, they can't tell what changed.

        That's a freshness problem, not a messaging problem.

        A notification system (email, push, in-app, preferences,
        digest, unsubscribe) is a 3-week project. A red dot on the
        nav icon that says "something new" ships this afternoon.

        One solves the symptom (they're not being told). The other
        solves the cause (they can't see what's new when they look).

        RECOMMENDATION: Reduce. Ship the dot. See if complaints drop.
        If they do, you just saved 3 weeks. If they don't, then build
        push notifications, but now you have data, not a guess.

You:    Makes sense. Let's do the dot.
You:    /nano
        [3 steps, 2 files, product standards: shadcn/ui + Tailwind]

You:    [builds it]

You:    /review
        Review: 2 findings (1 auto-fixed, 1 nit). 2 things done well.

You:    /security
        No secrets, auth changes, or unsafe data flows introduced. Grade A.

You:    /qa
        Opened the app, posted a reply, refreshed, confirmed the dot
        appears and clears. 4 checks pass.

You:    /ship
        PR explains why the change exists, how it was checked, and what
        remains. CI green. Sprint journal saved.

That is the difference: not just code generation, but a delivery loop you can inspect.

What changes after installing Nanostack