Skip to content

docs: add troubleshooting section and pre-install version check - #29

Draft
OS-joaocastilho wants to merge 2 commits into
mainfrom
docs-troubleshooting-and-version-gate
Draft

docs: add troubleshooting section and pre-install version check#29
OS-joaocastilho wants to merge 2 commits into
mainfrom
docs-troubleshooting-and-version-gate

Conversation

@OS-joaocastilho

Copy link
Copy Markdown
Contributor

Summary

Changes vs 0.6.3:

  • Add a "Before you install" section instructing users to verify the plugin is on the latest version. Autoupdate is proving unreliable and users stuck on 0.6.0 / 0.6.2 keep hitting the pre-fix install prompt.
  • Add a Troubleshooting section with symptom to fix mapping covering the four reported failure modes: "authenticate tool isn't loaded", "non-interactive session", "Server Disconnected" or "failed authorization" in Developer Settings, and Windows minimal PATH.
  • Document the Reset procedure (uninstall plugin, Help > Troubleshooting > Clear cache, restart, reinstall) as the recovery path when updates do not stick.
  • Add a "Getting logs" section pointing at the per-server bridge log paths on macOS, Windows, and Linux, so users can attach logs when asking for help.
  • Reword Step 5 of the Claude Code install prompt: the prior "Do NOT tell me to run /mcp -> outsystems -> Authenticate manually" line is now actively harmful, since the manual Authenticate step is currently the reliable rescue path across every reported failure. Reworded to allow it as a fallback when auto-auth does not trigger.
  • Bump plugin version 0.6.3 to 0.6.4.

No functional or recipe changes to the actual install commands.

Test plan

  • README renders correctly on GitHub with the new sections and anchor slugs.
  • Cross-link from Slack support threads to the Troubleshooting section resolves.
  • Plugin marketplace picks up 0.6.4 after merge and "Check for updates" surfaces the new version.

Changes vs 0.6.3:
- Add "Before you install" section instructing users to verify the plugin is on the latest version. Autoupdate is proving unreliable and users stuck on 0.6.0 / 0.6.2 keep hitting the pre-fix install prompt.
- Add Troubleshooting section covering the four reported failure modes: "authenticate tool isn't loaded", "non-interactive session", "Server Disconnected", and Windows PATH.
- Document the Reset procedure (uninstall plugin, Clear cache, restart, reinstall) as the recovery path when updates do not stick.
- Add "Getting logs" section pointing at the per-server bridge log paths on macOS, Windows, and Linux.
- Reword Step 5 of the Claude Code install prompt to allow the manual /mcp select outsystems Authenticate fallback instead of forbidding it. That fallback is currently the reliable rescue path across every reported failure.
- Bump plugin version 0.6.3 -> 0.6.4.

No functional or recipe changes to the actual install commands.
Changes vs previous commit on this branch:
- Rewrite the "non-interactive session" entry. The prior text told users to update the plugin, but this error also surfaces on the current plugin release when the mcp-remote bridge is configured but no OAuth token is cached yet. Update-the-plugin does not resolve it.
- Point users at the terminal-bootstrap workaround (npx -y mcp-remote https://<tenant>/mcp in a regular terminal), and clarify why: Claude Desktop's embedded agent runtime cannot open a browser tab from inside a chat turn, so token bootstrap has to happen out-of-process.
- Mention the equivalent Claude Code CLI path (claude mcp -> Authenticate in an interactive terminal) as an alternative for that surface.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant