Skip to content

v3.2.1 — the CLI reaches the resources, and doctor reports its real port

Choose a tag to compare

View all tags
@schequm schequm released this 31 Aug 22:03
· 1 commit to main since this release
v3.2.1
1b767f7

Added

customaise resources and customaise resource <name|uri>.

The server publishes four resources, and two of them are the only documents that say how to build a UserScript or an AgentScript. An MCP client gets them from resources/list for free. The CLI had no verb that reached any of them, so an agent driving Customaise from a terminal could install scripts and never learn how to write one.

That bit hardest exactly where the CLI is the only option: a cloud agent VM cannot attach a local MCP server at all, so its agent both most needed the conventions and was the only one that could not read them.

customaise resources
customaise resource agentscript-conventions
customaise resource userscript-conventions

A bare name is accepted, because that is what an agent reading the list will type. The primer that customaise init writes now points at them before the install loop.

Fixed

  • doctor reported the port it assumed, not the one the daemon is on. It read the WebSocket port from an environment fallback rather than the daemon's own record, so it could report 4050 while the daemon listened elsewhere. That made a local verification of the bridge meaningless: it confirmed the default, not the daemon.
  • A failed share says why. Sharing a script the server refused left the row silent and discarded the reason.

npm i -g @customaise/mcp@3.2.1 · Changelog

Assets 2
Loading