Skip to main content
Start with the specific failure and the selected project, host and provider. Keep the error message; it is more useful than repeatedly starting the same task.

An agent is missing or will not start

Try its CLI in your regular terminal. Check Settings → Agent CLI for detection and setup information. If you changed the shell’s PATH, reopen Dure so it can read the updated environment. For SSH work, repeat the check on the remote machine. If sign-in is required, complete the provider’s login and confirm the account has access to the tool or model. Dure does not supply provider credentials.

GitHub shows no repository or an access error

Select a local Git project with a GitHub remote, and check the desktop GitHub CLI:
Confirm that the signed-in account can read that repository, then refresh the GitHub sidebar. An organization or Projects permission error needs the appropriate GitHub access. See GitHub workflows.

A setting or plugin is missing

Use the settings guide for current locations in the Basic and Beta interfaces. Open Plugins in the sidebar to inspect compatibility and available settings, then refresh its catalog. A rejected or conflicting package is not an active integration; see plugins.

A task appears disconnected or ended

Inspect session state and actual files before launching another copy. Reconnect to living work; use the offered recovery action after the process ends. Record what completed so the agent does not repeat an external action. If the app lost its panes but an agent is still running, don’t start it again. Run dure ls --alive to find its session ID, then dure runs open <session-id> --space <space-id> to put the running session back in a pane without restarting it.

An attachment did not arrive

Wait for preparation/upload to finish before sending. Check the pane’s host, file path and transfer error, then retry the failed attachment. Provider image support varies; see terminal attachments.

An update or macOS launch fails

Check the installed version in Settings → General. Retry Check for updates if the check failed, or use the official DMG from Install Dure. Checking alone does not install anything. For a macOS warning, confirm the official download and follow Apple’s guidance. Do not disable security protections or force open a file reported as malware.

Collect a useful report

Include the app version, provider and CLI version, local/SSH context, exact action and error. Settings → Privacy and telemetry explains diagnostic reports you can review, then copy, save or send to the Dure team; the privacy page lists the anonymous usage data the app can send and how to turn it off. Remove credentials, private paths and unrelated conversations before sharing a report.