Skip to content

Choose a coding-agent workspace on Linux, macOS or Windows

Published

Choose Paneflow's installer for the operating system and CPU that will run the application, then install your coding agents in the shell where the project lives. A compatible terminal application does not make every agent, runtime or shell combination compatible.

Paneflow 0.17.4 installation matrix

The following artifacts were checked against the 0.17.4 release on October 1, 2026. Artifact availability is not an installation test on every machine. Paneflow is free software under GPL-3.0-or-later.

OSCPUInstallation referenceRuntime boundary
Linuxx86_64 or ARM64 (aarch64)Linux: AppImage, .deb, .rpm, .tar.gzWorking Vulkan driver and loader; package or standalone dependencies still apply.
macOS 13+Apple Silicon (aarch64)macOS: .dmg or HomebrewApple Silicon build; not an Intel binary.
Windows 10 1809+ or Windows 11x64 (x86_64)Windows: .msiWorking GPU driver, DirectX 11 feature level 10+, ConPTY terminal runtime.
macOS Intelx86_64No native artifact in this releaseDo not select the Apple Silicon DMG as a compatible installer.
Windows ARMARM64No native artifact in this releaseDo not treat the x64 MSI as a verified ARM installation.

The release's build targets, Linux package dependencies and Windows runtime reference ground this matrix. The mirrored Windows reference retains an older installer example; use the current installation page for filenames. An AppImage packages the application, not a missing GPU driver.

Check the agent in the intended shell

AgentActually checked for this guideOfficial platform guidance
Claude CodeWindows x64: claude --version reports 2.1.286; claude --help confirms interactive launchSetup documents macOS, Linux, native Windows and WSL. On native Windows, Git for Windows enables Bash; without it, the current docs describe the PowerShell tool. Native Windows sandboxing is not supported in those docs.
Codex CLIWindows x64: codex --version reports 0.159.2; codex --help confirms interactive launchCLI and Windows sandbox document native Windows as well as macOS/Linux. Windows 11 is recommended; updated Windows 10 is best effort. Native sandbox setup can depend on administrator-approved changes and device policy.

Agent sources were consulted on October 1, 2026. These version/help checks do not certify authentication, model execution, sandbox behavior, every shell, Linux or macOS. Other agents were not tested for this guide. Keep each agent's permissions and requirements separate from Paneflow's support matrix.

Native Windows or WSL?

For Windows repositories and tools, launch the native MSI-installed app from the Start menu or a native Windows shell. Choose your shell in Settings and verify the agent on its PATH. Installing an agent inside WSL does not install it in PowerShell, and the reverse is also true.

For a Linux-native toolchain already in WSL2, keep repository, dependencies and agents in that environment. The Windows installation reference describes the Linux build inside WSL2 with WSLg; its graphics requirements still apply. A WSL shell inside a native Paneflow pane is a separate choice from running the Linux application. Do not launch the native Windows app from a WSL host shell. This guide has not executed either WSL arrangement.

Codex's current WSL guidance offers that path for Linux tooling or workflows whose needs are not met by the native sandbox. It is not evidence that Windows requires WSL for all agents. Claude Code's native Windows and WSL sandbox capabilities also differ; follow its setup reference rather than assuming the terminal provides a sandbox.

Diagnose the layer that fails

  1. Check OS and CPU in system information. On Intel macOS or Windows ARM, the missing native artifact is the boundary; consult installation support rather than guessing an installer.
  2. If Paneflow cannot open a window, check the platform installation reference and GPU/runtime requirements, then troubleshooting. Changing agents cannot fix a missing graphics driver.
  3. If the app opens but claude or codex is unavailable, run its version command in that exact pane. Check PATH and whether you installed it in native Windows or WSL. Follow the agent's own setup instructions.
  4. If the CLI starts but cannot authenticate or run a model task, diagnose that agent's credentials, permissions, network and provider access. Reinstalling Paneflow does not establish those prerequisites.

Once the application and agent both work in the intended environment, use the worktree reference to separate parallel changes. Keep installation details in the platform reference instead of copying a different setup for every distribution or agent.

Latest articles

All posts

v0.17.4GPL-3.0-or-later

Launch your next agent in Paneflow.