Terminal Coding AgentsConfiguration

Terminal Coding Agents

Configuration

SpecStory CLI Configuration

This page is a quick reference for SpecStory CLI commands, flags, and the files created in your repo.

Note

Most users start with specstory run <agent>, then use sync for past sessions and watch for background capture.

Commands

CommandDescriptionExamples
versionDisplay the current SpecStory versionspecstory version
checkVerify if terminal agents are installed and accessible to SpecStoryspecstory check
runLaunch an agent and auto-save sessions to Markdown (and Cloud if logged in)specstory run claude
specstory run cursor
specstory run codex
specstory run droid
specstory run gemini
syncConvert past sessions to Markdown and optionally sync them to SpecStory Cloudspecstory sync
specstory sync -s <sessionId>
watchWatch for new agent activity and auto-save to Markdownspecstory watch
specstory watch cursor
specstory watch codex
specstory watch droid
specstory watch gemini
loginAuthenticate with SpecStory Cloudspecstory login
logoutSign out of SpecStory Cloudspecstory logout
helpShow help informationspecstory help
specstory help run

Note

specstory sync shows parsing progress and supports multiple session IDs: specstory sync -s <id1> -s <id2>.

Project scaffolding

The first run inside a project creates:

  • .specstory/ for state and configuration.
  • .specstory/history/ for exported Markdown.
  • .specstory/.project.json for project bookkeeping.
<project>/
└── .specstory/
    ├── history/           # Markdown session transcripts
    ├── debug/             # Debug logs (if --log enabled)
    │   └── debug.log
    └── .project.json      # Project bookkeeping

Note

History files are written to .specstory/history/ in the repo you run from.

Default behavior

  • Session storage: .specstory/history/ in the working directory.
  • Cloud sync: Enabled when logged in with specstory login unless --no-cloud-sync is provided.
  • Session sources: Reads from ~/.claude/projects/, ~/.cursor/chats/, ~/.factory/, ~/.codex/history, and ~/.gemini/tmp/<project_hash>/chats.
  • Output format: Markdown files stamped with the session timestamp.
  • Timezones: Use --local-time-zone to stamp file names and content in local time.

Flags

FlagDescriptionUsage
-c, --commandUse a custom terminal-agent command or argsspecstory run claude -c "claude --dangerously-skip-permissions"
-s, --sessionConvert a specific session to Markdownspecstory sync claude -s <sessionId>
--consoleStream log output to stdoutspecstory sync --console
--logWrite logs to ./specstory/debug/debug.logspecstory sync --log
--debugInclude debug-level output (requires --console or --log)specstory sync --log --debug
--silentSuppress non-error outputspecstory sync --silent
--local-time-zoneUse local timezone for file name and content timestampsspecstory sync --local-time-zone
--no-cloud-syncDisable cloud sync even when authenticatedspecstory run --no-cloud-sync
--only-cloud-syncDisable local markdown writing and only sync to cloudspecstory watch --only-cloud-sync
--no-usage-analyticsOpt out of usage analyticsspecstory sync --no-usage-analytics
--no-version-checkSkip the version checkspecstory run codex --no-version-check
--output-dirWrite Markdown exports to a custom directoryspecstory watch --output-dir ~/my-agent-sessions
-h, --helpShow help information for a commandspecstory -h
-v, --versionShow the current SpecStory versionspecstory -v

Info

The CLI wrapper favors convention over configuration. Most projects will never need to modify defaults.

Debugging

Use console streaming (--console) or log files (--log) to inspect details (--debug) on processing.

# Run interactively with verbose output
specstory run claude --console --debug

# Capture logs without console noise
specstory sync cursor --log

# Capture detailed logs
specstory watch --log --debug

Log output highlights:

  • --log output written to ./.specstory/debug/debug.log
  • Which session files are being parsed.
  • Where Markdown exports are written.
  • Errors encountered during capture or sync.