Get started
A fresh session.
A head start.
Connect Storybloq to your coding client.
Give the next session somewhere to begin.
01 / Connect
Your tools.
One shared memory.
Choose your client, then run both commands in your terminal.
Node.js 20 or later.
Claude Code or Codex installed.
Your AI provider may charge separately.
npm install -g @storybloq/storybloq@lateststorybloq setup --client claudeOnce setup finishes, restart Claude Code. Type /story into the Claude Code chat.
02 / Carry it forward
Your next session starts here.
Work naturally with your agent. Storybloq keeps the project context so you can come back and keep building.
01
Open a project
Open your project folder in Claude Code or Codex. Type the command below into its chat to load Storybloq. If this is your first time, your agent will guide you through setting up the project.
Type /story into the Claude Code chat.
What happens: Your agent introduces the project and its current state, or helps you set it up.
02
Record a story and a decision
Tell your agent what you want to build and any decision it should remember. A story is a piece of work you want to do.
Say this in chatRecord a story to add an empty state to the booking calendar. Remember that the API owns availability.
What happens: Your story and decision are saved in the project.
03
Save the handover
When you are ready to stop, ask your agent to write a handover. Storybloq guides it to capture what happened, what is unfinished, and what comes next.
Say this in chatWrite a handover.
What happens: Your agent saves the handover in .story/handovers/. Check that it includes your decision.
04
Start a new session
Open a new chat in the same project and type the command below again. Storybloq loads the project context for your agent, including recent handovers, decisions, and unfinished work. Pick up from there.
Type /story into the Claude Code chat.
What happens: Your agent recalls your story and decision. No need to paste the previous conversation.
Need a hand? Troubleshooting +
The shell cannot find storybloq
Open a new terminal after installation. Check node --version (20 or later), then storybloq --version. Check that your npm global binary directory is on PATH.
The skill or project tools are missing
Re-run the setup command for your selected client and restart it. Review setup output for registration errors. Do not assume setup succeeded just because npm installed the package.
The client loads the wrong project
Check the folder open in the client and the project name in its response. A parent directory may contain a shared .story/. Stop and select the intended project before creating or updating records.
The new session cannot recover the answer
Confirm the handover was actually saved and both sessions opened the same project. Ask the client to read the latest .story/handovers/ file and cite it. If manual loading is required, record that as the result rather than calling it automatic recovery.
An optional companion
See the work.
As it happens.
The Mac app is optional. Follow stories, phases, and handovers in a live view of your project files.
Explore the Mac appRequires macOS 15 or later.