Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/8BitTacoSupreme/flowstate/llms.txt

Use this file to discover all available pages before exploring further.

flowstate launch prints the exact command you need to run a tool natively inside a Claude Code session. FlowState prepares context files and then hands off execution to tools that work inside Claude Code sessions — GSD skills, slash commands, and similar extensions. flowstate launch bridges that gap by giving you the precise command to copy and run.

​
Synopsis

flowstate launch <tool> [phase] [OPTIONS]

​
Arguments

​
tool
string
required
The tool to launch. One of: gsd, research, strategy.
​
phase
integer
Phase number. Only applicable when tool is gsd. Omit to print the progress-check command instead of a planning command.

​
Options

​
--root PATH
string
default:"."
Project root directory. Used to construct the absolute cd path in the printed command.

​
Why launch instead of running directly?

GSD skill invocations (e.g. /gsd:plan-phase 1) are slash commands that only work inside an active Claude Code session. FlowState cannot invoke them directly via claude --print for the same reason you cannot run slash commands from your shell. flowstate launch prints the command you paste into your terminal to start the right Claude Code session from the right directory.

​
Tool behaviour

​
gsd — with a phase number

Prints the cd + claude command that opens a session in your project directory, then shows the GSD slash command to run for that phase: 
flowstate launch gsd 1

Launch command:

  cd /path/to/project && claude
  → /gsd:plan-phase 1
Copy the printed command, run it in your terminal, and type the → line when the Claude Code session opens.

​
gsd — without a phase number

Prints the progress-check slash command instead: 
flowstate launch gsd

Launch command:

  cd /path/to/project && claude
  → /gsd:progress

​
research

Research runs through flowstate init via claude --print (non-interactive mode), not as a native session command. flowstate launch research prints an explanatory comment to that effect: 
flowstate launch research

Launch command:

  cd /path/to/project && claude
  → # Research runs via flowstate init (claude --print)

​
strategy

Same as research — strategy is a claude --print bridge call launched by flowstate init: 
flowstate launch strategy

Launch command:

  cd /path/to/project && claude
  → # Strategy runs via flowstate init (claude --print)

​
Examples

Print the Phase 1 GSD planning command: 
flowstate launch gsd 1
Print the GSD progress overview command: 
flowstate launch gsd
Print the Phase 3 command for a project in a different directory: 
flowstate launch gsd 3 --root ~/projects/my-app

​
Notes

  • The → line in the output is a visual separator — type or paste only the text after the arrow into your Claude Code session.
  • GSD must be installed and its skills available in your Claude Code environment for the slash commands to work. Run flowstate status to check whether GSD is detected.
  • flowstate run <phase> produces similar output to flowstate launch gsd <phase> but uses a different header. Both call the same underlying launch_command("gsd", phase, root) function.

Build docs developers (and LLMs) love

Get started for freeTalk to us