Nanostack started as a minimal set of skills for Claude Code: think, plan, review, security, QA, and ship, each passing context to the next through local artifacts.
The recent releases turned that into something more practical for real work: easier to inspect, easier to extend, and more predictable when an agent is reading, writing, and shipping from a repo. v1.1.1 is the safety and security hardening on top of v1.1.0.
Highlights across the v1.1.x line:
- visual artifacts turn plans, reviews, security checks, QA output, and sprint journals into HTML you can open and read
- custom workflow stacks let you build your own phases on top of Nanostack, instead of adding one-off skills
- artifacts carry integrity checks, so gates and context loaders verify the evidence they read
- the test harness was reorganized into shared fixtures, a manifest, and a local runner, so it is easier to know what broke and why
What v1.1.1 adds:
- stronger guards around risky shell commands, path containment, credential redaction, and write protection
- the global gates (phase, budget) now run before any allowlist or in-project shortcut, so a safe-looking command cannot skip them
- cleaner logs and promoted context, so they no longer carry data they should not
- honest framing: /freeze is a guided instruction, not a hook-enforced block
Nanostack works with Claude Code, Cursor, OpenAI Codex, OpenCode, and Gemini CLI, with stronger enforcement where the host supports it.