Repository navigation
Usage call: which built-in tools and integrations do you rely on? #11338
Audacity88
started this conversation in
General
Replies: 1 comment 1 reply
What an upgrade must preserve: The tools-extra split needs to account for installed skills that invoke For Lucid/Qdrant memory-backend reports I have nothing to add (not used). |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We expect to release v0.9 in the next few days. We're gathering usage reports to guide changes to how ZeroClaw ships built-in tools and integrations. The goal is a smaller core with supported ways to add optional capabilities. Before deciding individual moves, feature gates, or removals, we want to know what people run and what an upgrade would need to preserve.
The tool inventory proposed in #11305 identifies 31 optional tools. Nine register on a default configuration today:
calculator,weather,pushover,screenshot,image_info,browser_open,http_request,web_search_tool, andbackup.The proposed
tools-extrasplit would include these tools in the standard distribution, while source builders would explicitly enable the broader bundle. Existing configurations and build instructions need an upgrade path. The current direction is recorded in the runtime delivery discussion.Which implementations do you use?
Reports about any of the nine tools above are useful. The other optional tools in the proposed inventory are:
browser,browser_delegate,text_browsernotion,jira,linkedin,composio,google_workspace,microsoft365project_intel,report_templateclaude_code_runnerdata_management,cloud_ops,cloud_patternsimage_gen,file_upload,file_upload_bundlediscord_search,email_search,email_readknowledgeWe also want reports about the Notion, Twitter/X, and Reddit channels, and the sandbox-bound
claude_code,codex_cli,gemini_cli, andopencode_clitools. These appear in the separate Schema V4 cleanup proposal under #8310 and #8754. The coding-CLI tools are currently classified as host-coupled in #11305.Lucid and Qdrant memory backends already have a usage call in #10344. Please add memory-backend reports there so that evidence stays together.
What would an upgrade need to preserve?
A short reply is enough. Please tell us:
Please leave credentials, tokens, private data, and full configuration files out of your reply. A sanitized description is enough.
Please reply as soon as possible, especially if a proposed change would affect your deployment. We'll review reports as they arrive and keep this discussion open after the v0.9 release for follow-up decisions. A quiet thread will be recorded as "no usage reported"; actual usage will remain unknown. Listing an implementation here does not announce its removal.
The accepted replacement-first policy in #6165 still applies to working integrations. Each concrete removal, feature gate, or migration needs its own issue and PR with a supported replacement path and review of configuration migration, security, compatibility, audit behavior where applicable, and rollback. The multi-model provider work in #9809 can proceed while this call is open.
All reactions