Tools Workflow¶
This guide covers the full lifecycle for tools in the packaged app: creating, importing, enabling, using, updating, publishing, taking down, and deleting.
Before you start¶
Use a model that supports tools.
For web search tools, choose at least one search engine in
Settings.For custom tools, only run code from sources you trust.
Open Tools Manager¶
Open
Chat.Click
Toolsin the composer area.Use the
Toolsmodal to manage built-in and custom tools.
Enable built-in tools¶
In Tools -> Built-in Tools, toggle:
Web SearchImage GenerationVideo GenerationMusic/SFX Generation
Notes:
If your selected model does not support tools, the app blocks enabling.
If your plan limit is exhausted for image/video/audio generation, enabling those tools may be blocked until usage resets.
Create a custom tool¶
Open
Tools->Create.Fill in core fields: *
Tool Name*Language*Functionality*Code FileConfigure optional metadata: *
Function Name,Description,Version,Website,Release NotesInput Parameters JSON Schema
Private User Inputs JSON
Choose visibility: *
Privatefor local-only use *UnlistedorPublicfor registry publishingSet an initial version number and provide a changelog description for the first version.
Dependencies: By default, the tool inherits the current system state. This means for most languages, if the package is present on the system, it can be used in your tool without additional configuration. For Rust, you can specify a list of cargo crates to be installed as you would with rust-script or cargo embedded manifest format.
Click
Create Tool.
After creation, the tool is added locally and can be toggled on in the same modal.
Import a custom tool¶
Open
Tools->Import.Paste a tool UUID.
Use
Fetch Infoto preview details.Click
Import.
Imported tools appear under Registry Tools and can be enabled for chat.
Use tools during chat¶
Built-in tools:
Keep the tool toggled on.
Prompt normally in chat; the model decides when to call tools.
For image/video/audio tool calls, the app shows an in-chat review panel so you can adjust options and approve generation.
Custom tools:
When a custom tool is requested, the app shows a permission dialog.
Review tool identity and source details.
To run it, confirm and type
RUNwhen prompted.Deny if you do not trust the tool or request.
- ..warning:: Exercise caution when running custom tools, especially those from
untrusted sources. They can execute code on your machine. Always review tool details and source code before confirming execution.
- ..warning:: For custom tools with web access, be mindful of potential data sharing with external services.
Review the tool’s functionality and permissions to understand what data may be transmitted.
..warning:: If you encounter unexpected behavior after enabling a tool, consider disabling it and reviewing its code or source for potential issues.
- ..warning:: Malicious tools can seriously harm your computer or data.
Only run tools from sources you trust, and always review the code if possible. InferencePort AI is not responsible nor is liable for any and all damage caused by custom tools.
Edit and update a custom tool¶
In
Tools, find the tool card and chooseEdit.Update code or metadata.
Save changes.
Versioning note:
When pushing updates to a published registry tool, your local version should be higher than the current registry version.
Publish and push updates¶
In
Tools, choosePublishfor a local tool.For already published tools, choose
Push update.Review the source diff summary and confirm.
The tool then appears in registry listings and can be imported by UUID.
Install the latest registry version¶
If a registry copy is newer than your local installed copy:
Open
Tools.Find the tool card marked as having an update.
Choose
Install latest.
Take down (unpublish) a tool¶
For tools you own:
Open
Tools.Choose
Take downon the published tool.Confirm removal from the registry.
This removes the registry listing but does not automatically delete every local installed copy on other devices.
Delete a local tool copy¶
Open
Tools.Click
Deleteon the tool card.Confirm deletion from this device.
This removes the local copy and also disables it if it was currently enabled.
Troubleshooting¶
Tool toggle does not stay on: verify model supports tools and limits are not exhausted.
Web search tool will not enable: set at least one search engine in
Settings.Import fails by UUID: confirm the ID is valid and still available.
Custom tool run blocked: review permission prompts and ensure you confirmed execution.