A file convention
A .story/ directory of JSON and markdown. Tracked by git. Readable by any AI. No database. No server. No SaaS.
Learn about the CLI →A memory for the machine
The local dashboard for Claude Code.
A file convention, a Mac app, and a multi-AI review loop that turns every coding session into a building block instead of a reset.
Free. Open file format. Your data stays in your repo.
The problem
Two ways to write code with a machine.
Same developer. Same AI. Same hour of the afternoon. The only difference is whether the session remembers the one before it.
Monday, 9:14 am
Vibe coding.
Start session. Read nothing.
Ask the AI what you should work on. It hallucinates context from three files and a prayer.
Produce code that may or may not fit. The architecture drifts by a degree. You won't notice for a week.
Close the tab. The session ends. Everything it learned dies with it.
Tomorrow you will have the same argument about the same function.
Monday, 9:14 am
Agentic development.
- i.The AI reads your spec, latest handover, open issues. Knows exact state.
- ii.It plans the work. A second AI reviews the plan.
- iii.You implement. Both AIs review the code.
- iv.You commit. A handover is written.
- v.Next session picks up where this one left off.
What it is
Three pieces. One idea.
No database. No dashboard. No SaaS login. A folder, an app, and a habit.
A native Mac app
Project state in a sidebar, Claude Code in an embedded terminal. Watches files, updates live. Free.
See the Mac app →A review loop
Your AI plans. A second AI critiques the plan. You code. Both AIs review. Independent verification every merge.
See how it works →The Mac App
See what Claude is doing in real time
A native Mac app that shows tickets, issues, and session handovers while Claude works. The board updates live as project files change.
“Most AI tools try to make the model smarter. Storybloq makes the system around the model smarter.”
Local to the project
No server, no account. Everything stays in your repo.
Updates in real-time
The board reflects what Claude is doing right now. Every change shows up instantly.
How it works
How it works.
1
Init
Run storybloq setup-skill in your project. It creates a .story/ directory and registers the MCP server with Claude Code.
storybloq setup-skill2
Work
Type /story at the start of each session. Claude loads your tickets, issues, roadmap, handovers, and lessons learned. It knows what was built, what's blocked, and what to do next.
/story3
Track
Create tickets for planned work, log issues for bugs you find, and capture ideas as notes. Then ask Claude to work on them.
4
Handover
At the end of a session, state is captured. Decisions, blockers, and next steps are preserved for the next session.
5
Dashboard
Open the Mac app to see live status: tickets in progress, issues discovered, roadmap phases, and session handovers.
Trust
Your project memory stays with your project.
Local .story/ files
JSON files in your repo, tracked by git, readable in any text editor.
No extra account. No hosted sync.
No server, no API key. Anonymous analytics and crash reports are on by default but you can opt out in Settings at any time.
Works with Claude Code you already use
Storybloq sits on top of your existing Claude Code workflow. No new IDE, no migration.
Autonomous mode is optional
Use it as a daily dev assistant. Turn on autonomy when the work is well-defined and you want hands-off execution.
Install
One command. Three places.
$npm install -g @storybloq/storybloq
$storybloq setup-skill
# that's it. your next session knows the last one.
Free. Ships through the Mac App Store. Your data stays in your repo.