Introducing ToolSmith: build, edit, and debug plugins with AI

ToolSmith enters Controlled Availability on September 22, 2026, bringing a conversational way to build and maintain plugins in Tool Studio.

Describe the workflow you want, review the proposed plan, and let ToolSmith help create and test the pieces behind it. You can also bring an existing plugin into the conversation to make a change or investigate a failure.

What you can do with ToolSmith

• Build a new plugin from a description. Explain the outcome and the systems involved. ToolSmith researches available APIs and existing assets, proposes a plan, and builds after you approve it.
• Edit an existing plugin. Describe what needs to change, review the proposed approach, and work through the update and testing in the same conversation.
• Debug a failing plugin. Provide the issue and relevant conversation context. ToolSmith can inspect execution logs, investigate the cause, and propose a fix.

For example, start with: “Build a plugin that shows my open Linear issues.” Or bring an existing plugin and ask: “Add a priority filter.”

Review the plan. Stay in control.

You can refine the plan in plain language before approving it. When credentials are needed, ToolSmith collects them through a secure configuration card. It also asks for approval before taking external actions, including tests that change data in connected systems.

Your conversation keeps the plan, progress, and results, so you can return and continue where you left off.

Join Controlled Availability

We’re starting with a selected group of customers who have a real workflow to build, edit, or debug and a participating developer with access to Tool Studio and the relevant third-party systems.

Interested? Request early access to ToolSmith by telling us about your team, the workflow you’d like to build or improve, and the systems it uses. Our team will review your nomination and coordinate next steps with your account team. Submitting a request does not guarantee access. Selected participants will receive a kickoff, guidance on their first use case, and ongoing opportunities to share feedback.

During CA, start with a focused workflow involving one or two systems. Results vary by system and workflow complexity, so review and test generated changes before relying on them. When editing shared assets, check their dependencies in Tool Studio because ToolSmith does not display those dependencies in the conversation.

Want to experience ToolSmith live? Join us at now[dev]26 in San Jose for two days of hands-on building with engineers and product teams.

What would you like to build—or improve—with ToolSmith? Tell us in the replies.