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 can be installed in two ways: via Flox for a fully reproducible, zero-configuration environment, or manually using a standard Python venv and pip. The Flox path is strongly recommended for new users — a single flox activate command provisions Python, Node, the Claude Code CLI, MCP servers, and FlowState itself in one step.

Installation Options

Verify Your Installation

After completing either installation path, confirm that FlowState and the Claude bridge are working correctly. Check the FlowState version:
flowstate --version
Expected output:
flowstate, version 0.2.0
Check the Claude CLI bridge:
flowstate check
Expected output when the bridge is correctly configured:
claude CLI found: /Users/you/.local/bin/claude
Timeout: 300s | Max turns: 10
If the claude binary is not found, FlowState will print:
claude CLI not found.
Install Claude Code or set FLOWSTATE_CLAUDE_BIN to the binary path.

Environment Variables

FlowState reads a single environment variable for runtime configuration:
VariablePurpose
FLOWSTATE_CLAUDE_BINOverride the path to the claude binary
If FLOWSTATE_CLAUDE_BIN is not set, FlowState auto-detects the claude binary by checking, in order:
  1. Your shell PATH
  2. ~/.local/bin/claude
  3. /usr/local/bin/claude
  4. /opt/homebrew/bin/claude
To set a custom binary path, export the variable before running FlowState commands:
export FLOWSTATE_CLAUDE_BIN="/path/to/your/claude"
flowstate check
For Flox users, if you use the Exa MCP server’s semantic search capabilities, copy the .env.example file and add your Exa API key:
cp .env.example .env
# Edit .env and set EXA_API_KEY=your_key_here
The Flox profile script automatically loads .env on each flox activate.

Build docs developers (and LLMs) love