Skip to content

Latest commit

 

History

History
60 lines (44 loc) · 2.5 KB

File metadata and controls

60 lines (44 loc) · 2.5 KB
title Troubleshooting
description Fix empty model pickers, unexpected prompts, and a profile that will not open.

Troubleshooting

Provider and key problems

The model picker is empty. Open Settings → Providers and add a key, import one from the environment scan, or set a local server URL. Then pick a model in the thread header.

The key will not save. The OS keyring may be unavailable. On Linux, install and unlock a Secret Service keyring or use an environment-only provider key. Plaintext persistence is off by default; the emergency compatibility path is to start Copse with COPSE_ALLOW_PLAINTEXT_SECRETS=1, then approve the separate per-save warning. The resulting base64 copy is not encrypted.

A hosted request fails immediately. Check the provider dashboard, the endpoint URL, and that the key has not been rotated. Copse talks to the provider directly — there is no Copse-side outage page.

LM Studio context resets after reboot. Copse cannot set LM Studio’s load context over the OpenAI-compatible API. Save the context length as that model’s default in LM Studio: Making LM Studio's context length survive a restart.

Approval and sandbox surprises

Everything asks, including ls. Either auto-run is off, the project is untrusted, or there is no sandbox (Windows, or init failure). Check Settings → Permissions and the project trust prompt.

git fetch asked on Windows but not on a Mac. On a Mac the sandbox is the boundary. On Windows there is no jail, so auto-approval does not fire at all and every recognised shape asks — reads included.

The Shells tab never asked. That tab is your terminal, not the agent. It is supposed to open without a prompt and without the sandbox. Agent commands still go through Approvals.

A command ran, failed, then asked. The sandbox blocked network or an outside path. The follow-up dialog is the unsandboxed retry.

Recovery

Quit Copse before copying ~/.copse/ (or COPSE_DIR). That directory is the whole profile. Step-by-step backup and restore: Backup and recovery.

Do not share settings.json, thread exports, or browser profiles without redacting them. Copse has no secret-scrubbed support bundle. See SUPPORT.md.

Still stuck

Search GitHub Issues. File a bug with the template. Suspected vulnerabilities go to security@copse.dev, not the issue tracker.