Pathrule Studio
The native macOS app for Pathrule. Code with Claude Code, Codex and OpenCode in one workbench, with the local runtime, MCP server, hooks and cache bundled in.
Pathrule Studio is the native macOS app, and the flagship Pathrule surface. It is where you code with your AI engines on top of your team's context, with the local runtime bundled in.
Studio puts Claude Code, Codex and OpenCode in one app. Start a thread with any engine, then switch models mid-conversation without losing the context you have built. An orchestrated mode lets a conductor model delegate subtasks across every engine at once. Your team's memories, rules and skills are delivered natively, scoped to the path you are working in, so the assistant knows your conventions before its first move. There is no separate daemon to install: the embedded MCP server, the hook supervisor, the local cache, and the AI client config writers all live inside the app.
What Pathrule Studio owns
- Your AI engines, in one app. Run Claude Code, Codex and OpenCode side by side, switch the model mid-conversation, and use orchestrated mode to fan a task out across engines. You bring your own engines; Pathrule makes them sharper. We do not sell AI subscriptions.
- Native context delivery. The hook supervisor reads the path scoped slice from the local cache and hands the right memories, rules and skills to the engine before its first action, with no MCP wiring to maintain.
- Knowledge authoring. Write and review memories, rules and skills at the path they belong to, with team comments and threads on each item.
- The workbench. Source control, Patterns, MCP servers and extensions, scheduled tasks, usage, an integrated terminal and run, all around the chat.
- Local folder attach. Bind a workspace to a directory on your machine. The runtime resolves your AI session's working directory to a workspace using that mapping.
- MCP server. The same MCP tool surface your assistant speaks to, running inside the app, available to Claude Code, Cursor, Codex, Windsurf, GitHub Copilot, and any MCP compatible client.
- Companion file sync. Writes and keeps the AI client config plus the managed companion files (
CLAUDE.md,AGENTS.md) in sync as content changes, and materializes your skills to disk where each client looks for them. Pathrule marks its own files and preserves any you already had, so your hand-written setup is never clobbered. - Offline, dark and light. Studio works offline and follows your system light or dark theme.
- Tray notifications and auto updates. Native OS notifications for suggestions, conflicts and team activity, and background updates applied on next launch.
What Pathrule Studio hands off to Web
Pathrule Web is the cloud management console. A few flows live there rather than inside Studio.
- Organization profile and settings, including ownership transfer.
- Members and roles: invite teammates and manage access.
- Plans and billing.
- Workspace admin across the org (rename, archive, export) and team usage.
First run
- Download from the macOS app page and open the app.
- Sign in through the browser based PKCE flow that launches on first run.
- Create or pick a workspace.
- Attach the workspace to the local directory you want it to cover.
- Pick the AI clients you use. Pathrule Studio writes their configs and registers the hooks.
After this, open a thread in Studio or your editor in the attached directory. The right memories, rules and skills arrive in context before the first tool call.
Coexistence with Pathrule CLI
Studio and Pathrule CLI can run on the same machine. They share the same local cache and the same workspace attachment table. The first runtime to claim a workspace owns its hook supervisor for that session.
If you cannot tell which runtime is active, run:
pathrule doctor
The doctor reports which runtime owns the workspace, where the cache is, and whether the AI client configs match.
When to use Pathrule Studio
Use Pathrule Studio when you want to code with Claude Code, Codex and OpenCode on top of your team's context, author knowledge visually, and have source control, MCP, tasks, usage, terminal and run in one place. It is the default recommendation for most users on macOS. A Pathrule Studio companion for iOS is coming soon, so you can pick up a desktop conversation from your phone.
If you live entirely in the terminal, prefer Pathrule CLI. To manage your organization, members and billing from any browser, use Pathrule Web.
What to read next
- Pathrule CLI for the terminal first runtime.
- How hooks work for what the supervisor inside Studio is doing.
- Quickstart for the first end to end session.