Why can my terminal find the CLI but OfficeCubs cannot?

The desktop process may have started with a different executable search path or before you installed the tool. Verify the real executable and point the teammate setup at it when automatic detection fails.

Before you begin

A work engine is the CLI process that performs the task. OfficeCubs supplies the task context and records its progress, while authentication, model availability and usage charges come from your chosen provider. Successful detection is a setup check, not proof that every model or task will work.

Steps

1. Run the CLI from your terminal to confirm installation.
2. Inspect its actual executable location.
3. Choose that executable in advanced teammate setup.
4. Restart OfficeCubs and check again.

Example

A shell alias that works interactively is not necessarily an executable file the desktop can launch. Use the installed binary or supported launcher path.

Check the result

Check that the displayed path exists and then run a minimal task through the selected teammate.

Limits and troubleshooting

Avoid copying arbitrary shell startup commands into a task brief. Fix tool configuration at the setup layer.