Orchestrator

VS Code × Codex × Jira, in one free, open-source Mac app.
Repository browsing, Codex conversations, Kanban tasks and local code review.

 ·  MIT licensed  ·  macOS 15+

Download · Feature tour · Build from source · Documentation · Contribute

Experimental community beta. Version 0.2.0-beta.3 supports Apple Silicon and Intel with signed in-app updates. It is ad-hoc signed and not notarized by Apple. See the release acceptance record for validation scope and limitations.

Orchestrator is an independent project, not an OpenAI product. Browser, Computer Use and plugin integrations are experimental and may require separately installed upstream components.

Download and install

Download for Apple Silicon · Download for Intel · All releases

Requires an Apple Silicon or Intel Mac running macOS 15 or later. No development tools or source build are needed to install the app.

1. Download Orchestrator_aarch64.dmg for Apple Silicon or Orchestrator_x86_64.dmg for Intel.
2. Open the disk image and drag Orchestrator into Applications.
3. Eject the disk image, then open Orchestrator from Applications.
4. Sign in with your own supported Codex account and add a workspace to get started.

macOS may block the first launch because this beta is not notarized. Read the first-launch security guidance before deciding whether to open it. Never disable Gatekeeper globally.

Updates download on click. Use the account menu to download an available update, then choose Install and restart. If in-app updating is unavailable, Download latest version opens Releases directly. See the installation and update guide for details.

Your work, in context

Start with a prompt, keep the conversation alongside your workspace, and follow the agent's work as it happens.

Chat, Files, Kanban, Subagents and Review use the maintainer's native macOS captures from 17 September 2026 and the fictional Taskboard Demo. Account details are removed; task results, diffs and activity are preserved. See the capture notes for the source revision and demo-only presentation change. Click any screenshot to view it at full size.

Feature tour

Inspect file contents

Expand a workspace in the sidebar and select a file to read its contents beside your conversation or Kanban board. Syntax highlighting and line numbers make code and configuration easy to inspect without leaving the chat.

Organise work with Kanban

Turn ideas into cards and follow each task from preparation through execution and review. Select the target branch in the board toolbar for new card branches and pull requests. Chat and Kanban share the same workspace, so you can choose the view that fits the work.

The board shows the existing demo tasks: one to do, two awaiting local review and two completed. The target-branch selector sits before refresh and archive.

See what subagents are doing

Inspect a delegated task's original instruction, conversation and activity without losing the parent conversation.

Review changes before publishing

Browse changed files, inspect the diff and decide whether to approve the work or request changes. Repository-specific review keeps changes understandable in both single- and multi-repository workspaces.

Understand your activity

Explore local run activity, token totals and outcomes by workspace and date range. Account usage limits are shown separately using the limits Codex actually reports for the selected plan.

The screenshot shows demo-project activity, not personal account quotas or a performance benchmark.

More ways to work

• Plans and Goals: Review a proposed plan before implementation, or pursue an explicit longer-running goal.
• Generated-image previews: Explore concepts in the conversation; copy images into a project when you explicitly request an asset.
• Multi-repository workspaces: Give agents the workspace context and review changes repository by repository.
• Keyboard navigation: Use ⌘4 for Chat, ⌘5 for Kanban, ⌘K for actions, ⌘N for a new chat and ⌘/ for shortcut help.
• Optional integrations: Explore Plugins, Browser and Computer Use with their experimental requirements and limitations.

Build from source

You need macOS, Xcode Command Line Tools, Node.js 24, npm and Rust 1.96.0. Build each architecture on matching hardware. Normal AI tasks require your own supported Codex account; GitHub authentication is separate.

git clone https://github.com/zachealy1/orchestrator.git
cd orchestrator
npm ci
npm run tauri dev

Build hooks prepare the pinned official standalone Codex engine, GitHub CLI and third-party notices, verifying the runtime downloads. No private-repository access or publishing credentials are required. Ordinary Chat and repository workflows do not require the Codex desktop app, Homebrew or a separately installed Codex CLI. Orchestrator does not redistribute private ChatGPT components.

Run checks or create a local development build

npm run lint
npm test
npm run test:release
npm run check:release
npm run build
cargo test --locked --manifest-path src-tauri/Cargo.toml
# Local ad-hoc package for development, not public distribution:
npm run tauri build -- --bundles app

A successful build does not establish public-release readiness. See the contribution guide and release acceptance checklist.

Installation and updates

The 0.2.0-beta.3 community release targets Apple Silicon and Intel. Use the download instructions above for a first installation, including when moving from an existing 0.1.0 build.

To update manually, back up important data, finish all tasks and repository operations, quit Orchestrator, then replace the Applications copy with the newer installer from Releases. See the installation guide and recovery guidance.

The community release workflow publishes independently signed updater packages and advances the feed only after both architectures finish. No Apple account or paid update service is required. Packaging verifies integrity; a clean-machine installation or two-version update rehearsal is not claimed for this release. See the release record.

Documentation and support

• Installation and updates · Troubleshooting and recovery
• Privacy and local storage · Permissions and integrations
• Public download and clone reports · Reporting setup and definitions
• Report a bug · Report a vulnerability privately
• Contribute · Architecture · Screenshot capture notes

Production releases share minimal daily installation activity with PostHog by default. You can disable this in Settings → Privacy → Share installation activity; see the privacy guide for the exact data collected. Download reports use GitHub's aggregate asset counters: downloads are not users or successful installations. AI tasks and connected integrations still communicate with their providers; see the privacy guide before sharing sensitive work.

Licence

Orchestrator's original source is MIT licensed, copyright Zac Healy. Dependencies, bundled runtimes and third-party assets retain their own licences and notices. Packaging generates a third-party inventory; it does not relicense those components. package.json remains private: true to prevent accidental npm publication.

GitLab reviews

Connect GitLab from Settings → Connections → GitLab. GitLab.com supports browser sign-in or a personal access token; self-managed hosts use a personal access token with the api scope. Multiple hosts can be connected at once, with one account per host. Credentials use macOS Keychain; CLI configuration is kept in Orchestrator's app data directory. Disconnecting a host leaves its saved card review links intact.

When a card finishes, Orchestrator checks each repository's origin. If all repositories have connected GitHub or GitLab destinations, it publishes draft review requests, including mixed-provider cards. Otherwise it uses local review and explains which connection is missing. You can publish from local review before local merging starts. GitLab requests display !number; cards move to Done after all requests merge or have nothing to publish. Closed, unmerged requests stay in review.

Self-managed instances require HTTPS with normal certificate verification. Custom HTTPS ports, SSH origins, and nested groups are supported. Pushes use the connected account over HTTPS. Custom SSH hostname aliases, GitLab subpath installations, fork-based requests, pipelines, and merging through the app are outside this integration.

For development, npm run prepare:gitlab-cli-runtime installs the pinned GitLab CLI runtime for the current Mac architecture, and npm run test:gitlab-cli-runtime checks its version, integrity, and configuration isolation. Native runtime preparation and release validation include GitLab automatically.