claude-code - 💡(How to fix) Fix [Feature Request] Add directory validation for GitHub project context in `/ultrareview` command [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49534Fetched 2026-04-17 08:38:24
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/johannes/.local/share/claude/versions/2.1.112 (expected in multi-process scenarios)\n at Od_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n at Ke6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.795Z"},{"error":"Error: Plugin MCP server error - mcp-config-invalid: MCP server greptile invalid: Missing environment variables: GREPTILE_API_KEY\n at djH (/$bunfs/root/src/entrypoints/cli.js:2748:30115)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.809Z"}]

Root Cause

⏺ The ultrareview completed but produced empty output. PR #289 doesn't exist in xxx/yyy — the repo's highest PR number is 8, and the current branch <branchname> has no open PR. The review likely failed
  silently because the target PR couldn't be found.

Code Example

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/johannes/.local/share/claude/versions/2.1.112 (expected in multi-process scenarios)\n    at Od_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n    at Ke6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.795Z"},{"error":"Error: Plugin MCP server error - mcp-config-invalid: MCP server greptile invalid: Missing environment variables: GREPTILE_API_KEY\n    at djH (/$bunfs/root/src/entrypoints/cli.js:2748:30115)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.809Z"}]

---

The ultrareview completed but produced empty output. PR #289 doesn't exist in xxx/yyy — the repo's highest PR number is 8, and the current branch <branchname> has no open PR. The review likely failed
  silently because the target PR couldn't be found.                                                                                                                                                                                      
                                                                                                                                                                                                                                         
  Did you mean a different PR number, or would you like me to open a PR for this branch first?
RAW_BUFFERClick to expand / collapse

Bug Description /ultrareview used the wrong GH project and hence could not find the branch [Image #1] It was my fault as was in the wrong directory - it would had been nice if this mistake would have been detected beforehand

Environment Info

  • Platform: darwin
  • Terminal: intellij
  • Version: 2.1.112
  • Feedback ID: 7581c1fd-5b3f-46bf-b18b-8a117274b322

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/johannes/.local/share/claude/versions/2.1.112 (expected in multi-process scenarios)\n    at Od_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n    at Ke6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.795Z"},{"error":"Error: Plugin MCP server error - mcp-config-invalid: MCP server greptile invalid: Missing environment variables: GREPTILE_API_KEY\n    at djH (/$bunfs/root/src/entrypoints/cli.js:2748:30115)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T21:01:23.809Z"}]

As /ultrareview returned with an empty result I would expect to not count down the actual /ultrareview count

⏺ The ultrareview completed but produced empty output. PR #289 doesn't exist in xxx/yyy — the repo's highest PR number is 8, and the current branch <branchname> has no open PR. The review likely failed
  silently because the target PR couldn't be found.                                                                                                                                                                                      
                                                                                                                                                                                                                                         
  Did you mean a different PR number, or would you like me to open a PR for this branch first?

extent analysis

TL;DR

The issue can be resolved by ensuring the correct GitHub project and branch are used with the /ultrareview command, and setting the required environment variables, such as GREPTILE_API_KEY.

Guidance

  • Verify that the correct directory is being used when running the /ultrareview command to avoid targeting the wrong GitHub project.
  • Check the environment variables, specifically GREPTILE_API_KEY, to ensure they are set correctly to prevent plugin errors.
  • Review the output of the /ultrareview command to identify any silent failures or missing PRs, and adjust the command or environment as needed.
  • Consider implementing a check to detect and prevent the use of the wrong directory or missing environment variables before running the /ultrareview command.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to incorrect usage and environment setup. Ensuring the correct directory and environment variables are used can help resolve the issue. However, the exact solution may depend on the specific requirements and setup of the project.

Recommendation

Apply workaround: Set the correct environment variables, such as GREPTILE_API_KEY, and ensure the correct directory is used when running the /ultrareview command. This should help prevent errors and silent failures.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Add directory validation for GitHub project context in `/ultrareview` command [1 participants]