When a project is bound to a workspace that declares integration tools, those tools run on the local datamate engine. If no usable engine is present, the CLI says so in a 10-second toast:
Workspace "X" declares N integration tools. They run on the local engine, which is not installed. Install it with: npm i -g @altimateai/datamate
Two problems with that:
- It disappears. The toast auto-dismisses after 10 seconds. If you were reading the model's output — which is where your attention is on the first turn — you miss it, and nothing tells you again that turn.
- There is nothing to act on. The command is text in a toast. You cannot run it, and you cannot copy it without selecting it by hand.
The result is a bound workspace whose declared tools silently do not work, with the explanation shown once and then gone.
In headless run it is worse: a toast cannot render at all, so there is no signal whatsoever that the workspace's tools are missing.
Expected: the CLI should offer to fix it — install the engine, or hand over the exact command — and should not require the user to have caught a transient toast. It should never install anything without being asked.
When a project is bound to a workspace that declares integration tools, those tools run on the local
datamateengine. If no usable engine is present, the CLI says so in a 10-second toast:Two problems with that:
The result is a bound workspace whose declared tools silently do not work, with the explanation shown once and then gone.
In headless
runit is worse: a toast cannot render at all, so there is no signal whatsoever that the workspace's tools are missing.Expected: the CLI should offer to fix it — install the engine, or hand over the exact command — and should not require the user to have caught a transient toast. It should never install anything without being asked.