Choose a workspace engine

If your organization has enabled the preview, you can choose OpenCode or Claude Code when creating a new local or cloud workspace. The engine runs the conversation and tools; the model is the AI you choose within that workspace.

💡

Preview availability: this choice is offered only to organizations enabled for the preview. If you do not see it, your existing workspace setup continues to work. Contact your administrator about availability.

Choose the engine when you create a workspace

The Workspace engine choice appears in the new-workspace form when available. An existing workspace keeps its engine and conversation history. To try the other engine, create a separate workspace.

  1. Start a new workspace.Choose a local workspace or cloud workspace.
  2. Choose the engine.Under Workspace engine, select OpenCode or Claude Code.
  3. Open a chat.Create the workspace. For a workspace running Claude Code, open the model picker to check your account connection.

OpenCode uses your organization's configured models and billing. A workspace running Claude Code uses your own Claude account or your organization's own provider credential for Claude models. Harriet managed credits do not pay for Claude-model usage in that workspace.

Connect your Claude account

Use Connect your Claude account in the model picker to start Claude Code's official sign-in flow. Follow the terminal instructions and browser link. On a local Windows installation, the flow opens in a separate terminal window.

When sign-in finishes, the panel shows Connected. Your normal Claude account limits and billing apply. Do not paste account tokens or API keys into the chat. Harriet does not ask you to copy an account token from another application.

If Claude later refuses your sign-in because it expired or was revoked, Harriet says so and offers Connect again. A scheduled task that needs your account stops and emails you instead of retrying.

To disconnect, open the same panel and select Disconnect account. If you send a message while your account is not connected, Harriet keeps the message in the composer and opens the Claude account panel. Connect, then send it again.

Claude Code runs commands, edits files and fetches web pages without asking, unless your organization requires approval. When it does ask, choose Always allow to stop asking about that tool in this workspace. Organization rules that require approval always ask.

To see or undo what you chose Always allow for, open Skills and connectors, open a connector's menu and choose Approvals. Remove one tool, or clear them all, and Claude asks again. These choices are yours alone: nobody else in a shared workspace sees them.

A skill that cannot be loaded, for example because it uses hooks, is left out and named on the Skills page with the reason; it does not stop your other skills. In a shared workspace only skills the workspace owner saved are loaded.

Use an organization key

Your administrator can configure the organization's own provider key in Harriet's bring-your-own-key settings. Sync your Harriet account after the administrator makes a change. The model picker then reports that your organization provides its own Claude credential.

EU-hosted Claude choices require the organization's own supported provider credential. Connecting a personal Claude account does not turn it into an EU-hosted connection. See EU data residency for the distinction.

Switch models within a conversation

The model picker shows the models enabled for this workspace. Select a model there to continue the conversation with it. If a turn is already running, let it finish before the new model takes over.

Additional models appear only when enabled for the preview. They use your organization's configured Harriet model connection and do not require a Claude login. If none are listed, connecting Claude or asking your administrator about model access are the available next steps.

Work in a shared cloud workspace

Each person connects their own Claude account when a shared workspace uses account sign-in. A collaborator's turn never borrows the owner's saved login. An organization-provided credential may also be available.

Scheduled tasks run for the task owner. If that owner's Claude connection expires, the task stops with a reconnect notice instead of repeatedly retrying. The owner can reconnect and retry the task. Shared-workspace permissions and safety checks still apply; see working in a shared workspace.

What differs in the preview

Some workspace features are not available with this engine yet, including voice conversations, undo/redo, and conversation forks. Unsupported controls are hidden or explain that the operation is unavailable. Your existing OpenCode workspaces keep their usual features.

For general model access and sync troubleshooting, see choosing models and sign-in and sync.