Extension Tools
Settings → Extension Tools is the master switch table for the tools Croli hands an agent on top of its own inside a conversation.
These tools belong to no CLI; Croli injects them itself — which is not the same thing as the MCP screen, where you plug in third-party MCP servers of your own. The subtitle states the rule that matters most:
Each is injected when the agent starts, so a change applies to agents started afterwards.
Which means flipping a switch does not affect the conversation already running — only the next start counts.
The switches
| Switch | What the agent gets | Default |
|---|---|---|
| Live Feedback | Reports progress to you while it works, instead of bottling it up until the end | Off |
| Ask user question | Pops a multiple-choice question for you to settle when it is stuck, instead of guessing | On |
| Get session info | Reads the metadata of the current session | On |
| Read and drive the built-in browser | Reads page content, clicks, fills forms, navigates | Off |
| Run code in the built-in browser | Runs JavaScript it wrote itself on the page | Off |
| See and use your desktop's windows | Computer use: reads and drives the windows you share | Off |
| Create scheduled tasks | Creates scheduled tasks | Off |
Seven rows in all, and only two are on by default — Ask user question and Get session info. The rest you turn on by hand.
The delegation switch is not on this screen. delegate_to_agent is a Croli-injected tool too, but its switch lives only on Collaboration — the panel at the bottom of the Agents page.
Hit Save when you are done; success says "Tool settings saved".
A few dependencies
- Run code in the built-in browser depends on Read and drive the built-in browser — with that one off, this one is greyed out. And even with both on, the page still has to be shared at Read and act, and it is bound by the "Run without asking / Ask me every time" choice in Browser Use.
- See and use your desktop's windows only injects the tool; what it can actually see is decided by the Computer Use screen and by your own sharing: the master switch has to be on, and you share windows one at a time.
- When an agent has Let the agent handle files and commands turned on, it does not get the delegation tools — that switch hands the whole business of files and commands back to the CLI itself.
Saving writes by group
The UI is one table, but it is saved as six separate groups. A save writes only the groups that changed and leaves the untouched ones as they are — so two windows with settings open at once do not overwrite each other.
Once saved, workspace windows catch up immediately; there is no need to reopen them.