Docs

Integrations

FlyDocs connects your AI coding tools, version control, and project management into one workflow.

FlyDocs sits between three categories of tools: where your code lives, where your work is tracked, and where you build. Each connection serves a distinct purpose in the workflow, and they all operate through the same methodology.

Three Connection Points

How FlyDocs Connects

AI Coding Tools Where you build Cursor, Claude Code, Warp, Codex, Windsurf
Version Control Where code lives GitHub, GitLab, Bitbucket
Project Management Where work is tracked Linear, Jira, and more coming
AI tool reads FlyDocs files locally → FlyDocs relay API connects to PM and VCS providers in the cloud

AI Coding Tools

FlyDocs integrates at the IDE level through installed files: skills, hooks, commands, and agent definitions. Your AI coding tool reads these files locally and follows the methodology they define. No running server, no network dependency for local operations.

  • Cursor: generated rules and commands in .cursor/
  • Claude Code: full integration via .claude/ directory with skills, hooks, commands, and agents
  • Warp: AGENTS.md with context and workflow instructions
  • Codex: AGENTS.md with context and workflow instructions
  • Windsurf: AGENTS.md with context and workflow instructions
  • Other agents: AGENTS.md compatibility mode for any tool that reads it (e.g. GitHub Copilot)

Read the full AI coding tools guide for configuration details, hook support, and cross-platform behavior.

Version Control

FlyDocs uses your version control provider for repo scanning (detecting your stack), linking repos to workspaces, and the PR creation workflow. Connect via OAuth through the FlyDocs portal.

  • GitHub: org/account level access, repo scanning, PR workflow hooks
  • GitLab: group/project access, repo scanning, MR workflow
  • Bitbucket: workspace/repo access, repo scanning, PR workflow

Read the version control guide for provider setup and PR workflow details.

Project Management

The FlyDocs relay API translates workflow operations into provider-specific API calls. Your scripts call the relay, the relay resolves workspace config, and the provider receives native requests.

  • Linear: full coverage via GraphQL adapter, issues, transitions, comments, milestones, cycles
  • Jira: full coverage via REST adapter, JQL-based queries, all workflow operations
  • Coming soon: Trello, Notion, ClickUp, Asana, and more

Read the project management guide for provider configuration, status mapping, and the relay architecture.

Cross-Platform by Design

FlyDocs generates configs for all supported tools simultaneously. The methodology is the same, the workflow is the same, and the skills are the same. What changes is the config format: .cursor/ for Cursor, .claude/ for Claude Code, and AGENTS.md for everything else. A team using different AI tools still follows one process.

Next