> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowdeck.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# FlowDeck for Mac vs FlowDeck CLI

> Choose the right FlowDeck product for your workflow

FlowDeck comes in two forms designed for different workflows. Most developers use both.

## Feature Comparison

| Feature               | FlowDeck for Mac       | FlowDeck CLI              |
| --------------------- | ---------------------- | ------------------------- |
| **Best For**          | Day-to-day development | Automation & CI/CD        |
| **Interface**         | Native macOS app       | Terminal commands         |
| **AI Agent**          | Built-in               | Via skill pack install    |
| **Build & Run**       | ✓                      | ✓                         |
| **Testing**           | Visual test results    | JSON output for pipelines |
| **Simulators**        | Visual management      | Full command control      |
| **Physical Devices**  | ✓                      | ✓                         |
| **Log Streaming**     | Integrated panel       | Terminal streaming        |
| **Source Control**    | Built-in               | —                         |
| **UI Automation**     | Agent-driven           | Full command control      |
| **CI/CD Integration** | —                      | Designed for pipelines    |
| **JSON Output**       | —                      | ✓                         |

## When to use FlowDeck for Mac

<CardGroup cols={2}>
  <Card title="Day-to-day development" icon="window">
    A full IDE experience with a native UI — build, test, and debug without touching the terminal.
  </Card>

  <Card title="AI-assisted development" icon="robot">
    The built-in agent handles multi-step tasks in plain language: fix bugs, run tests, automate the UI, commit changes.
  </Card>

  <Card title="Simulator & device management" icon="mobile-screen-button">
    Manage simulators and physical devices from a visual panel.
  </Card>

  <Card title="Source control" icon="code-branch">
    Stage, commit, and push without leaving FlowDeck.
  </Card>
</CardGroup>

## When to use FlowDeck CLI

<CardGroup cols={2}>
  <Card title="CI/CD pipelines" icon="gears">
    Machine-readable JSON output integrates cleanly with GitHub Actions, GitLab CI, Jenkins, and other pipelines.
  </Card>

  <Card title="Terminal-first workflows" icon="terminal">
    Keyboard-driven development from the command line, with an interactive TUI mode.
  </Card>

  <Card title="External AI agents" icon="wand-magic-sparkles">
    Install the FlowDeck skill pack to give Claude Code, Codex, or other agents direct access to the Apple toolchain.
  </Card>

  <Card title="Scripting and automation" icon="code">
    Scriptable build and test commands with consistent exit codes and structured output.
  </Card>
</CardGroup>

## Using both together

Many developers use both products:

* **FlowDeck for Mac** for day-to-day development — writing code, running the app, testing, debugging
* **FlowDeck CLI** for CI/CD pipelines and scripted automation

<Note>
  FlowDeck for Mac and FlowDeck CLI maintain separate configurations and do not share project state.
</Note>