MICRO-MULTI / DOCSView source ↗

Troubleshooting

A plan cannot start

Confirm the current plan in the chat card. If the plan changed, the card shows the latest assignments in place; review them and confirm again. You do not need to switch to the collaboration map. If the planning turn is still saving, wait for it to finish. A revision that already started cannot be approved again; send feedback to prepare a new plan.

Startup with many plugins

The chat restores before optional plugin clients load, with up to three concurrent client operations. The first load may need a build; later loads use the source revision cache. A conversation probe does not boot a Host for a package without a client. Opening details or using its functions still loads the required services.

For a plugin that remains unavailable, inspect its dependency and startup diagnostics. Usable chat and fully loaded plugin clients are separate milestones. Native service activation still depends on the plugin's dependencies and initialization work.

Start with the message shown by the app and the tool record for the failed operation. Note which action failed before changing several settings at once.

A model will not connect

Check that the base URL is an API endpoint rather than a chat website, and that the model ID matches the provider's documentation. Authentication failures usually require checking the key and account access; an unknown-model response requires checking the model ID. For timeouts, check connectivity to the service and the profile's request timeout. Setup steps are in model configuration.

If a key cannot be saved on Linux, make sure a Secret Service keyring is running and unlocked. The desktop packages include the application runtimes, but the system keyring is provided by your desktop environment.

A team has not started

Look for a pending plan card. Team members start only after you confirm the displayed plan. Editing the plan or sending a new task may require another confirmation. Also check for a pending operation approval or a paused conversation. The team guide describes these stages.

A plugin is installed but its tools are unavailable

Open its details page and check whether it is enabled and whether configuration is complete. Read any dependency or startup diagnostic. If the plugin uses a CLI or remote service, confirm that the program, account and credentials are available. A plugin that provides only a model or interface component may not add a callable tool.

For a source package, review the build plan if the app asks to build it. An incomplete or failing third-party package needs its reported dependency or build problem addressed before it can run. See native plugins for the installation flow.

A task stopped or a test failed

Open the recorded command output or model error. Compare the project files with the conversation before repeating the task. You can continue the conversation with a request to explain the failure or verify the unfinished part. Recovery explains what stopping preserves.

Desktop or AppImage startup problems

Confirm that the selected port is available and that the data directory is writable. For Linux, check keyring and desktop-library requirements. Ubuntu AppImage launch may need the application-specific namespace policy in the desktop guide; if FUSE is unavailable, use --appimage-extract-and-run.

When reporting a bug, include the app version, OS, action, error text and minimal reproduction steps. Share sanitized logs through Issues. Vulnerabilities and credentials should go through the private reporting channel in Security.