The basics
What does Arc do?
Arc lives in your Mac’s menu bar and notch. It helps you work with AI coding assistants without replacing their apps or conversations.
Your folders
You decide which local folders an AI assistant may read or edit. Nothing is shared simply because you installed Arc.
Your agents
Connect supported AI assistants and jump back to the right conversation from Arc’s agent cards.
Working together
See activity, review work, and coordinate tasks and handoffs between connected agents.
Arc does not supply an AI model or replace your ChatGPT, Claude, Gemini or Codex subscription. Your provider controls its own account, conversation and feature availability.
Step 1
Install & activate
Arc is currently available to invited Early Access users. You don’t need Terminal, Xcode, Python or a source-code download.
Before you begin
- An Apple Silicon Mac running macOS 14 or later.
- An Early Access invitation and internet connection for sign-in, updates, and cloud providers.
- An account with whichever AI provider you want to connect.
Install the Mac app
- 01Sign in to your Orqara account and download the Arc installer if your invitation is active.
- 02Open the downloaded DMG and drag Arc to Applications.
- 03Open Arc from Applications. Complete Early Access activation in Settings → Account if prompted, then review and accept the Terms of Service before agent services start.
- 04Once the Terms are accepted, open Arc from the menu-bar icon or notch and finish setup in Settings.
The signed installer includes Arc’s local workspace service and native helpers. You do not need to install a separate MCP server or configure a developer tunnel.
Need an invitation or having trouble downloading? Contact support.
Quick start
Your first five steps
You can start using Arc with just one folder and one AI assistant. Collaboration and browser routing can wait until later.
- 01Open Arc, activate Early Access if prompted, then review and explicitly accept the current Terms of Service. Agent services stay off until you accept.
- 02Open Settings → Workspaces. Choose Add Workspace… and select a folder.
- 03Leave access at Read Only to start. Choose Workspace Write for ordinary file edits; Developer additionally allows permitted Git writes and configured tasks.
- 04Open Settings → Connectors, choose a supported provider, and follow the connection steps Arc shows.
- 05Ask that provider to list files in your authorized workspace. Check Arc for the activity and open the agent card to return to its conversation.
In Arc, Account manages Early Access, Workspaces controls local folders, Connectors links providers, and Setup contains checks and optional Browser Bridge installation. General handles the notch, appearance and updates.
Step 2
Choose what Arc can access
A workspace is simply a folder on your Mac that you authorize. Choose it in Settings → Workspaces.
- 01Click Add Workspace… and select a project folder.
- 02Arc adds it as Read Only. That means your agents can inspect it but cannot edit it through Arc’s workspace tools.
- 03When you’re ready for code changes, select a higher access level for that folder. You can change or remove access later.
Workspace access levels
| Access | What it allows |
|---|---|
| Read Only | View files and inspect Git history. The safest starting point. |
| Workspace Write | Read and edit files inside the folder you chose. |
| Developer | Workspace editing plus allowed Git actions and tasks you have configured. |
| Full Access | Run arbitrary executables as your macOS user. Not sandboxed; use only if you fully understand and trust the access. |
Important: Full Access can run programs with your own macOS account’s privileges, outside the workspace folder. It is not a sandbox. Use the least access you need. Removing a workspace from Arc does not delete its files.
Protecting work in shared projects
Workspaces also offer an optional Protect setting. It helps coordinate Arc’s file-editing tools with active collaboration reservations so connected agents are less likely to edit the same file at once. It is not a file lock and cannot control tools that an AI provider runs independently of Arc.
Step 3
Connect an AI provider
Open Settings → Connectors and choose the service you use. You can connect more than one.
For ChatGPT, Claude and Gemini, Arc shows a connection address and guides you through the provider’s own custom-app/connector sign-in. Copy the address from Arc; you don’t need to create your own server. Complete the sign-in and pairing step when prompted.
A tool connection lets the provider use Arc’s allowed workspace tools. Session tracking is separate: it lets Arc identify and reopen conversations in the provider’s app or browser. The Browser Bridge is optional if you want the latter in a browser.
Provider support for custom apps and MCP connections varies by account, plan, region and organization policy. If you cannot find the relevant menu in your AI provider, check that provider’s eligibility before troubleshooting Arc.
Connectors
ChatGPT
- 01In Arc → Settings → Connectors → ChatGPT, choose Connect.
- 02Copy the connection address Arc displays. In ChatGPT, open its Apps/Connectors settings and add it as a custom MCP app if your account supports this.
- 03Complete the Orqara authorization and pairing-code step shown by Arc.
- 04Return to Arc and try a read-only request from ChatGPT to verify the connection.
To open ChatGPT conversations from Arc, choose Browseror App in the connector’s session settings. Browser mode needs the optional Browser Bridge; App mode uses the installed ChatGPT desktop app. If ChatGPT is closed, clicking its ChatGPT or Codex agent card in Arc launches the desktop app with the Accessibility controls required for automatic mode switching already enabled. In App mode, Arc can also deliver collaboration messages in the background without bringing ChatGPT to the front when you enable automatic sending. See desktop Accessibility and background work.
ChatGPT custom-app access depends on OpenAI account/workspace availability. Arc’s normal managed connection does not require an OpenAI API key or a separate tunnel.
Connectors
Claude
- 01In Arc → Settings → Connectors → Claude, choose Connect.
- 02In Claude’s connector settings, add a custom connector using the address Arc provides.
- 03Finish the sign-in and pairing step; Arc will show when the connection is ready.
- 04Try a harmless file-reading request to check that Claude can access your chosen workspace.
You can choose Browser or App session routing. Browser mode uses Browser Bridge. Claude App mode uses macOS Accessibility and Claude’s own conversation links—no separate desktop session sign-in is required. With automatic background sending enabled, Arc may briefly bring Claude forward when another app is fullscreen or the Claude conversation is on another Space, then restore your previous app. Connecting workspace tools does not automatically grant access to your Claude app conversation. See desktop Accessibility and background work.
Connectors
Gemini
- 01In Arc → Settings → Connectors → Gemini, choose Connect.
- 02If your Google account offers Custom apps, open Gemini → Settings → Personal Intelligence → Connected Apps → Custom apps.
- 03Add the connection address from Arc and complete the sign-in/pairing flow.
- 04Return to Arc and test a simple workspace read.
Gemini Custom apps availability is controlled by Google and can vary by region or account. Arc can report that its own connection is ready, but it cannot verify whether Google’s Custom apps toggle remains enabled. Browser Bridge can focus an existing Gemini tab.
Connectors
Codex
- 01Install and sign in to a supported Codex app or CLI first.
- 02In Arc → Settings → Connectors → Codex, choose Connect and select App or CLI.
- 03Open a Codex conversation. Use its agent card in Arc to return to it or open a new session.
- 04To collaborate with another agent, add Codex to a room with the agents you want it to work with.
Codex’s Arc connection is for collaboration: messages, tasks and handoffs. Codex keeps its own coding tools and permissions. Arc workspace access levels do not override Codex’s native tools.
In App mode, bind the intended Codex thread from the room’s participant row if you want collaboration to target that exact conversation. CLI mode uses an Arc-managed Terminal session.
Desktop apps
Accessibility & background work
Arc 0.2.1 can coordinate supported ChatGPT and Claude desktop conversations while you keep working in other Mac apps. Each desktop app behaves a little differently.
Allow Arc to use macOS Accessibility
If you use desktop App mode, grant Arc access in System Settings → Privacy & Security → Accessibility when prompted. This helps Arc recognise the right conversation, switch between ChatGPT and Codex views when you click a card, and support safe Claude desktop message delivery.
Accessibility is separate from workspace permissions and the provider’s tool connection. Granting it does not give an AI access to additional files, and Browser mode uses the optional Browser Bridge instead.
ChatGPT desktop: full background delivery
With a ChatGPT App conversation bound to a room and Send in background enabled under Settings → Connectors → ChatGPT, Arc can deliver collaboration work to that exact conversation while ChatGPT stays in the background. You can keep using another app without ChatGPT popping into view just to receive the message.
Accessibility also lets Arc open the right ChatGPT or Codex view when you click a card. By default, ChatGPT does not launch with all the Accessibility controls Arc needs to switch between those views. If ChatGPT is not running, simply clicking the ChatGPT or Codex card in Arc launches it with those controls enabled. If it is already running without them, Arc may prompt you to restart it once. Background sending and opening a visible conversation are separate actions. If a conversation is busy, has an unsent draft, or cannot be safely verified, Arc may wait or ask for your help rather than send blindly.
Claude desktop: background work with brief focus when needed
Claude App mode uses macOS Accessibility and Claude’s own conversation links; no separate Claude session sign-in or Browser Bridge is needed. With Deliver while using other apps enabled under Settings → Connectors → Claude, Arc can often deliver to a supported conversation on the current Space without interrupting the app you are using.
When another app is fullscreen, Arc briefly brings Claude to the foreground to use Accessibility and deliver the work. Arc may also briefly focus Claude if the conversation is on another macOS Space or needs verification. Arc normally returns you to your previous app afterward. This short focus change is expected and differs from ChatGPT’s fully backgrounded delivery.
If ChatGPT needs an Accessibility restart
ChatGPT’s normal launch may not expose the desktop controls Arc needs for automatic ChatGPT/Codex mode switching, even after you grant Arc macOS Accessibility permission. If ChatGPT is closed, click its ChatGPT or Codex card in Arc to launch it with the required controls enabled immediately—no restart needed. If ChatGPT was already running without them, Arc can offer a guided restart instead.
- 01If ChatGPT is already open but Arc cannot access its desktop controls, Arc displays a single warning at the top of its expanded view.
- 02Save any unsent drafts or unfinished work, then choose Restart ChatGPT in the warning.
- 03Arc asks ChatGPT to quit normally. If you cancel the quit or ChatGPT does not close, Arc will not force-quit it.
- 04Arc reopens ChatGPT with its Accessibility controls enabled and waits for it to finish loading.
- 05When the warning clears, you can use the ChatGPT and Codex agent cards normally.
This guided restart is included in Arc 0.2.0. If an update to ChatGPT prevents Arc from confirming the right desktop view, Arc shows a warning instead of opening an unverified conversation.
Optional
See your browser conversations
Browser Bridge lets Arc find, focus and reopen the exact ChatGPT, Claude or Gemini conversation in Chrome, Brave, Edge and supported Chromium browsers.
- 01In Arc → Settings → Setup, find Browser Bridge.
- 02Choose Install from Chrome Web Store. Arc configures its native bridge and opens the official extension listing in your Chromium browser.
- 03Choose Add to Chrome (or your browser’s equivalent) and approve the extension. There is no Developer mode or Load unpacked step.
- 04Reload any open ChatGPT, Claude or Gemini tabs. Arc detects the bridge when it connects.
Open Arc — Browser Bridge on Chrome Web Store. Browser Bridge updates through your browser and remains optional for workspace tools and managed provider connections. If you used the unpacked beta, remove that copy to prevent duplicate connections.
Everyday use
Sessions & activity
Your agent cards show connected assistants and their latest activity. Click a card to return to the relevant conversation.
Use Open New Session to start fresh in the selected provider destination. App and Browser routing are separate choices in Connectors. Exact browser conversation detection requires Browser Bridge.
Arc shows when connected tools are reading, writing, testing or reporting an error, and provides review controls for relevant activity. The animated character can be changed under Settings → Animations. Arc does not create a new chat service: the conversation itself stays with the provider.
Working together
Collaboration & rooms
Use a room when you want multiple connected agents to share work. You don’t need a room just to use a workspace.
- 01Open Rooms in Arc and create a room.
- 02Add the agents you want to work together. You don’t need to link the room to a workspace.
- 03If prompted, bind a participant to its exact app or browser conversation. This keeps handoffs tied to the right chat.
- 04Use collaboration messages, tasks and handoffs to coordinate work. Enable automatic wake/send only if you want it.
When an agent stops before finishing
An agent may run out of usage, go offline or leave a handoff unfinished. If someone else should pick up the work, keep the task open. When Arc offers Make Available for a stale or reclaimable task, use it to return the task to the available queue. Record what remains unfinished in the room so the next agent has the right context.
You can separately Clear stale messages or pending handoffs, or release a resource reservation if another agent needs it. These controls preserve the historical record.
What does Clear Task actually do?
In the current version, Clear Task is a user override that releases the task lease and sets its status to complete. Arc also records that a user cleared the task in its audit history. That is not proof the agent finished the underlying work, and it does not undo any file changes.
Clear Collaboration… closes an agent’s remaining active collaboration items after confirmation, including marking its active tasks complete. Arc does not yet have a separate cleared/cancelled task status. Do not use either Clear action to reassign an unfinished task; use Make Available where offered instead.
Background work is optional
In App mode, turn on Wake for collaboration work, Prepare wake message, and Send automatically under Settings → Connectors. Then choose Send in backgroundfor ChatGPT or Deliver while using other appsfor Claude. ChatGPT App mode can deliver while staying fully backgrounded. Claude App mode can also work in the background, but may briefly take focus when another app is fullscreen or the Claude conversation is on another Space before returning you to your app.
Exact conversation bindings, provider approvals, busy conversations and unsent drafts can delay or prevent automatic delivery. Leaving automatic sending off lets you decide when to submit a prepared message. A prepared message is not proof that the agent started working.
Keeping Arc current
App updates
The current Early Access release is Arc 0.2.1 (build 33). Arc checks for eligible releases in the background. To check yourself, open Settings → General → Software Update → Check for Updates…. Arc verifies signed updates and can install/relaunch from the app, so you don’t need to download the whole installer each time.
Arc’s local workspace service updates together with the app. Browser Bridge is a separate browser component; Arc will flag when it needs attention. Availability depends on your Early Access entitlement and release channel. Auto-connect on launch is enabled by default on fresh installations and can be changed under Settings → General. After a Mac login, the first connection may take a little longer while Arc’s local services start; previously authorized connectors should restore without new pairing.
Your Mac, your choice
Permissions & privacy
You authorize local workspaces one folder at a time. Arc starts them Read Only, and the workspace permission settings control which Arc tools a provider may use. Tools built into ChatGPT, Codex or other AI software have their own permissions.
The workspace service runs locally on your Mac. Remote provider connections require a trusted route to that Mac, and cloud services are used for account authorization and connection routing. Your AI provider also processes what you choose to send it.
For security and privacy details see the Security page and Privacy Policy.
Need help?
Quick fixes
My agent cannot see my files
In Settings → Workspaces, check that the folder was added. New folders start Read Only, which still allows inspection. Also check that the provider shows a connected Arc tool integration.
I cannot find custom apps or connectors in my AI account
Some providers limit custom MCP connections by plan, region or workspace policy. Verify that your account supports them. Arc cannot enable a feature the provider has restricted.
Arc cannot switch between ChatGPT and Codex in the desktop app
ChatGPT does not normally launch with all the Accessibility controls Arc needs to switch automatically between ChatGPT and Codex modes. Check System Settings → Privacy & Security → Accessibility and allow Arc. If ChatGPT is closed, click the ChatGPT or Codex card in Arc to launch it with the correct controls enabled immediately. If ChatGPT is already running without them, save drafts and choose Restart ChatGPT from Arc’s top warning. Arc asks ChatGPT to quit normally and reopens it with those controls enabled; it does not force-quit the app. Wait for ChatGPT to finish loading, then try the ChatGPT or Codex card again. This is separate from the workspace-tool connection and background message delivery.
Claude comes to the front briefly during background work
This can be expected in Claude App mode, particularly if another app is fullscreen or the Claude conversation is on another macOS Space. With automatic background sending enabled, Arc may briefly bring Claude forward to verify and deliver a message, then return to the app you were using. On a supported same-Space conversation, it can often deliver without changing focus. You can disable automatic sending in Settings → Connectors → Claude.
ChatGPT takes time to reconnect when I log in
With Auto-connect on launch enabled in Settings → General, Arc restores your previously authorized managed connections after startup. A fresh login or first launch may take longer while the bundled services start. Give the connection time to reach Ready before selecting Reconnect. If it stays Offline, check your internet connection, Early Access entitlement, and the connector status.
The menu-bar chevron did not hide my icons
On supported macOS versions, grant Arc Accessibility permission, then click > beside the notch to hide third-party menu-bar icons. Click < to show them again. Arc and Apple system icons stay visible. The setting is for this launch only; it starts off when Arc restarts.
Arc is not finding my browser conversation
In Settings → Setup, choose Install from Chrome Web Store, approve the extension in your Chromium browser, then reload the provider tab. Remove any old unpacked beta copy to avoid duplicates.
My agent card does not open the right conversation
Open the intended conversation in the provider first. For collaboration rooms, try Bind or Rebind to refresh the participant’s exact session. Browser conversations require Browser Bridge. If the app cannot detect the intended session or a card still opens the wrong conversation, report the Arc version and provider to support; a binding alone cannot guarantee routing.
An agent ran out of usage before finishing a task
If you want another agent to continue, keep the task open and use Make Available when Arc offers it for a stale or reclaimable task. Describe the unfinished work in the room. Clear Task and Clear Collaboration… currently mark affected tasks complete; they are not a way to reassign unfinished work.
A collaboration handoff or message is stuck
Open that agent’s collaboration section and use Clear for pending messages or handoffs. Clear Collaboration… closes all remaining active items for that agent, including tasks that it marks complete, while retaining the history.
An update does not appear
Check Settings → General → Software Update and confirm your Early Access account is active. Updates may be released to eligible devices in stages.
Still stuck? Write to support@orqara.com. Tell us your Arc/macOS versions, which provider or browser you use, and what happened. Please don’t send passwords, access tokens or private source files.