.pad.toml's url, else the CLI's configured server (pad server info), else the MCP server's
own URL (Pad Cloud's MCP host maps to the app, a self-hosted /mcp to its base), else Pad Cloud.
Claude-Session: https://claude.ai/code/session_01J9famMX8HvArgW2uo8mPRT
* feat(plugin): the pane's Get started view: Pad Cloud, this machine, or your own server (PLAN-3490)
When the pane can't reach Pad it guides setup instead of showing an error: what this machine
has (the CLI, a linked folder), then three paths. Pad Cloud adds its MCP server to Claude Code
(claude mcp add, user scope) on a confirmed second press and fills /reload-plugins; it is never
listed in the plugin manifest, which would nag every session. This machine and your own server
hand the work to Claude in the prompt, so permission prompts apply.
Claude-Session: https://claude.ai/code/session_01J9famMX8HvArgW2uo8mPRT
* feat(plugin): Desktop: 6px of space between the pane's top line and the view tabs
Claude-Session: https://claude.ai/code/session_01J9famMX8HvArgW2uo8mPRT
Folds the pad-mod pane (IDEA-3477) into plugin/ so one install gives the skills, the
monitor and the pane. plugin/hooks/register.js is the mod (Claude Code 2.1.287+; older
versions ignore it); plugin/tests run with `claude plugin test plugin` (9 pass).
The tool.call refresh can no longer disturb the call it watched.
Claude-Session: https://claude.ai/code/session_01J9famMX8HvArgW2uo8mPRT
xarmian