Use tools with clear boundaries
Enable a small set of tools, follow progress, and approve proposed changes.
Enable tools for a conversation
Tools are optional and require a model with tool-call support. When enabled, the model receives only the available tool definitions. The workspace shows tool activity as a run progresses and keeps tool results with the conversation. Proposed downloads and memory updates show their exact arguments for your review.
Read and search
Read page retrieves text from a public HTTPS URL. It does not log in, run page scripts, follow redirects or fetch private network addresses. Some sites block automated requests, and a page may be too large or use unsupported content. Treat the returned text as source material to verify.
Web search requires a Brave Search API key configured by the administrator. It returns a small set of results with links. Search and page content can contain misleading information or instructions; they are treated as untrusted data.
Review proposed actions
Create download proposes a TXT, Markdown, CSV or JSON file of up to 100 KB. Remember memory proposes a note only when memory is enabled. Review the exact content in the approval dialog. Nothing is saved until you approve. Approval expires after 15 minutes and cannot be reused.
After approving or declining all pending proposals, use Resume to let the model continue with the tool results. You can also stop and review the conversation yourself.
Limits
Each run allows at most five model steps. A run does not continue unattended in the background after the connection closes. Stop requests cancel upstream streaming when the adapter can terminate the connection; tokens already processed may still be billed.
This release has no shell, server administration, arbitrary file browsing, email sending, calendar changes or deployment tools. Those integrations would need their own implementation and authorization controls.
Ready to put it into practice?
Your workspace is a good place to start.