Docs

Local Mode

Use FlyDocs without an account. Full methodology, file-based tracking, all skills and hooks, completely offline.

FlyDocs works without a cloud account. The local tier gives you the full methodology, file-based issue tracking, all skills and hooks, and deterministic enforcement for a single project. No account, no API key, no network dependency.

What You Get

  • Full methodology: the complete workflow lifecycle from capture to close
  • File-based issue tracking: issues stored as local markdown files, same commands, same enforcement
  • All skills and hooks: 7 hooks across 5 event types, skill-led reasoning, slash commands
  • Single project support: one project directory, fully self-contained
  • Deterministic enforcement: stop gates, transition validation, auto-formatting, all active
  • Stack detection and context: project context, knowledge base, and skill recommendations

What You Do Not Get

  • PM tool integration (Linear, Jira)
  • The FlyDocs dashboard and portal
  • Team features and shared workspaces
  • Multi-project support
  • Relay API access
  • Cross-repo service descriptor sync

Good For

  • Evaluation: try the full methodology before committing to a cloud account
  • Solo projects: individual work where a PM tool is overkill
  • Offline development: air-gapped or disconnected environments
  • Learning the methodology: understand how FlyDocs works before scaling to a team

This is not a crippled trial. The local tier is genuinely useful for solo development. The methodology, enforcement, and skills are identical to the cloud tier. The only difference is where issues are stored and whether they sync with an external tool.

How It Works

The unified client (flydocs_api.py) reads the tier from .flydocs/config.json. When the tier is local, all operations route to the local file backend instead of the relay API. Scripts never check tier directly. The routing is transparent.

.flydocs/config.json 
{
  "tier": "local",
  "provider": {
    "type": "local"
  }
}

Every slash command, every hook, every skill works the same. The only difference is that issues.py create writes a local markdown file instead of calling Linear or Jira through the relay.

Next