Skip to content

docs(troubleshooting): work briefing Jira unreadable — headless claude -p loads claude.ai connectors only; log in to the connector, not the plugin - #86

Merged
LiminCode merged 1 commit into
mainfrom
docs-jira-connector-login
Nov 20, 2026
Merged

LiminCode merged 1 commit into
mainfrom
docs-jira-connector-login

Conversation

@LiminCode

Copy link
Copy Markdown
Owner

Summary

Docs only. The work briefing's Jira section reported that the claude.ai Atlassian connector was rejected and needed a new login; re-authenticating the Atlassian plugin in the WSL Claude Code did not help. Probing the headless run showed why: claude -p loads claude.ai connectors and stdio servers only, and the plugin's HTTP OAuth MCP servers (Atlassian, Slack) never appear in the system/init event, silently, while interactive claude mcp list shows them connected (upstream anthropics/claude-code#36309, closed by the bot, unfixed). The fix on the user side is claude mcp login "claude.ai Atlassian", not the plugin. This PR records the mechanism and the diagnosis path so the next expiry does not need re-investigation.

What changed and why

  • docs/troubleshooting.md: one more symptom row; new section "无界面 claude -p 里的连接器" — the two tool routes (connector vs plugin), what -p loads and what it silently skips (measured on Claude Code 2.1.329, 2026-11-19), the claude mcp list / claude mcp login steps, how to read the real server/tool list from the stream-json init event instead of asking the model, and the "Two Claude Code config files exist" warning (~/.claude.json moved to ~/.claude/.config.json; the panorama's WSL probe still reads the old path).
  • docs/work-assistant.md: the "two tool-name prefixes" bullet now says only the connector set is actually in use in headless runs and points to the troubleshooting section.

Performance

Exempt: documentation only, no runtime behaviour changes.

Real-machine run

Exempt from the product run; the facts in the docs come from these probes on this machine (WSL, Claude Code 2.1.329, company account):

  • claude mcp list (login shell): claude.ai Atlassian … ! Needs authentication, plugin:atlassian:atlassian https://mcp.atlassian.com/v2/mcp (HTTP) ✔ Connected, plugin:slack:slack ✔ Connected.
  • Headless claude -p --model haiku --output-format stream-json --verbose --max-turns 1 with the briefing's flags and again plain: system/init.mcp_servers lists GitKraken (stdio), plugin:interstellar-plugin:interstellar (stdio, failed) and 30 claude.ai … connectors (Slack / Gmail / Calendar connected, both Atlassian entries needs-auth); no plugin:atlassian / plugin:slack entry, no mcp_server_errors; 116 and 145 tools, none containing "tlassian". A one-turn haiku run asked to list its tool names agreed (116 names, no Atlassian). Cost of the probes: under $0.04 total.
  • The last briefing (09:00 today, before the plugin re-auth) had an empty permission_denials list, so nothing was blocked by the allow-list; the tools were simply absent. Briefing content is company material and is not reproduced here.

Tests

tests/test_pr_report_discipline.py (doc registration and relative links): passed. Nothing else is affected.

Docs

  • CHANGELOG.md: not needed (no user-visible behaviour change)
  • Topic doc under docs/ updated (troubleshooting.md, work-assistant.md)
  • ADR: not needed

🤖 Generated with Claude Code

…新认证插件没用,要 claude mcp login

- docs/troubleshooting.md:症状表加一行;新增一节「无界面 claude -p 里的连接器」:两条路(连接器 / 插件)、
  -p 里插件的 HTTP OAuth 服务器不出现(2.1.329 实测,上游 #36309)、排查命令(claude mcp list / claude mcp login)、
  用 stream-json 的 init 事件核对、两份配置文件告警
- docs/work-assistant.md:「两种工具名前缀」那条补上实际只有连接器那套在用,指向排障手册

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@LiminCode
LiminCode merged commit 64678d2 into main Nov 20, 2026
0 of 3 checks passed
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