mirror of
https://github.com/anthropics/claude-code.git
synced 2026-02-19 04:27:33 -08:00
Compare commits
40 Commits
claude/sla
...
v2.1.2
| Author | SHA1 | Date | |
|---|---|---|---|
|
553d6ffc3e | ||
|
|
7b600bca3b | ||
|
|
4700be03eb | ||
|
|
9b08c1010b | ||
|
|
f34e2535b4 | ||
|
|
4297e57ef1 | ||
|
|
0d0221fd0a | ||
|
|
5aac2b1b6a | ||
|
|
2bb8af55fa | ||
|
|
a19dd76dcf | ||
|
|
63eefe157a | ||
|
|
870624fc15 | ||
|
|
2c3884689b | ||
|
|
03129a27b0 | ||
|
|
a3df424857 | ||
|
|
0b86fdb0e0 | ||
|
|
c2022d3698 | ||
|
|
e515f50dff | ||
|
|
24ad98a95f | ||
|
|
5c92b97cc4 | ||
|
|
d213a74fc8 | ||
|
|
52115592ba | ||
|
|
5d2df70860 | ||
|
|
b8a2ffb38f | ||
|
|
9fd556d947 | ||
|
|
b31e2fd182 | ||
|
|
d2cb503247 | ||
|
|
5fe61207ff | ||
|
|
1ed82e6af0 | ||
|
|
2a61cb364c | ||
|
|
6880bcbace | ||
|
|
4392352687 | ||
|
|
c27c6f4e4a | ||
|
|
0dde1fef97 | ||
|
|
e4f682030b | ||
|
|
eb87245010 | ||
|
|
3680637065 | ||
|
|
2192c86c20 | ||
|
|
dfd3494132 | ||
|
|
e8cca9a7af |
@@ -1,5 +1,5 @@
|
||||
---
|
||||
allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh api:*), Bash(gh issue comment:*)
|
||||
allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(./scripts/comment-on-duplicates.sh:*)
|
||||
description: Find duplicate GitHub issues
|
||||
---
|
||||
|
||||
@@ -11,28 +11,13 @@ To do this, follow these steps precisely:
|
||||
2. Use an agent to view a Github issue, and ask the agent to return a summary of the issue
|
||||
3. Then, launch 5 parallel agents to search Github for duplicates of this issue, using diverse keywords and search approaches, using the summary from #1
|
||||
4. Next, feed the results from #1 and #2 into another agent, so that it can filter out false positives, that are likely not actually duplicates of the original issue. If there are no duplicates remaining, do not proceed.
|
||||
5. Finally, comment back on the issue with a list of up to three duplicate issues (or zero, if there are no likely duplicates)
|
||||
5. Finally, use the comment script to post duplicates:
|
||||
```
|
||||
./scripts/comment-on-duplicates.sh --base-issue <issue-number> --potential-duplicates <dup1> <dup2> <dup3>
|
||||
```
|
||||
|
||||
Notes (be sure to tell this to your agents, too):
|
||||
|
||||
- Use `gh` to interact with Github, rather than web fetch
|
||||
- Do not use other tools, beyond `gh` (eg. don't use other MCP servers, file edit, etc.)
|
||||
- Do not use other tools, beyond `gh` and the comment script (eg. don't use other MCP servers, file edit, etc.)
|
||||
- Make a todo list first
|
||||
- For your comment, follow the following format precisely (assuming for this example that you found 3 suspected duplicates):
|
||||
|
||||
---
|
||||
|
||||
Found 3 possible duplicate issues:
|
||||
|
||||
1. <link to issue>
|
||||
2. <link to issue>
|
||||
3. <link to issue>
|
||||
|
||||
This issue will be automatically closed as a duplicate in 3 days.
|
||||
|
||||
- If your issue is a duplicate, please close it and 👍 the existing issue instead
|
||||
- To prevent auto-closure, add a comment or 👎 this comment
|
||||
|
||||
🤖 Generated with [Claude Code](https://claude.ai/code)
|
||||
|
||||
---
|
||||
|
||||
@@ -1,221 +0,0 @@
|
||||
# ANT_ONLY_METADATA_USER_ID Implementation Specification
|
||||
|
||||
## Overview
|
||||
|
||||
This document specifies the implementation of the `ANT_ONLY_METADATA_USER_ID` environment variable feature for Claude Code. This feature allows internal Anthropic jobs (like Claude Oracle, Oncall, Ambient, etc.) to pass custom metadata through Claude Code sessions to the Anthropic API for tracking, rate limiting, and incident triage purposes.
|
||||
|
||||
## Background
|
||||
|
||||
From the Slack discussion:
|
||||
- Internal API jobs launched via Claude Code currently lack user metadata showing `job_id` or `username` in `api_usage`
|
||||
- ~85% of requests from heavy CC users (like Closing The Loop org) have no user_metadata or job identifier
|
||||
- This metadata is critical for:
|
||||
- Managing Internal API rate limits
|
||||
- Triaging incidents
|
||||
- Setting up alerting that pings the DRI researchers
|
||||
- Understanding which jobs are driving token usage
|
||||
|
||||
## Requirements
|
||||
|
||||
1. **Environment Variable**: Claude Code must read an environment variable called `ANT_ONLY_METADATA_USER_ID`
|
||||
2. **API Integration**: The value must be passed to all Anthropic Messages API calls in the `metadata.user_id` field
|
||||
3. **Tree Shaking**: Only Anthropic internal builds should be able to use this feature
|
||||
4. **Format**: The expected format is a JSON object: `{"user": "<anthropic_username>", "job": "<job_name>"}`
|
||||
- Example: `{"user": "tedm", "job": "tedm-1208-mu-g-18x"}`
|
||||
- Or: `{"user": "vinke", "job": "claude-oracle:fluorine:vinke"}`
|
||||
|
||||
## Implementation
|
||||
|
||||
### 1. Environment Variable Reading
|
||||
|
||||
In the appropriate configuration/env module (likely `src/config/env.ts` or similar):
|
||||
|
||||
```typescript
|
||||
// Environment variable for Anthropic internal builds only
|
||||
// This is used to pass job metadata to the API for usage tracking
|
||||
export function getAntOnlyMetadataUserId(): string | undefined {
|
||||
// Only available in Anthropic internal builds
|
||||
if (!isAnthropicBuild()) {
|
||||
return undefined;
|
||||
}
|
||||
return process.env.ANT_ONLY_METADATA_USER_ID;
|
||||
}
|
||||
```
|
||||
|
||||
### 2. API Request Metadata
|
||||
|
||||
When constructing API requests to the Anthropic Messages API, add the metadata:
|
||||
|
||||
```typescript
|
||||
// In the API client module (e.g., src/api/anthropic.ts)
|
||||
import { getAntOnlyMetadataUserId } from '../config/env';
|
||||
|
||||
function buildApiRequestMetadata(): Record<string, string> | undefined {
|
||||
const metadataUserId = getAntOnlyMetadataUserId();
|
||||
|
||||
if (!metadataUserId) {
|
||||
return undefined;
|
||||
}
|
||||
|
||||
return {
|
||||
user_id: metadataUserId
|
||||
};
|
||||
}
|
||||
|
||||
// When creating a message:
|
||||
const response = await client.messages.create({
|
||||
model: selectedModel,
|
||||
max_tokens: maxTokens,
|
||||
messages: conversationMessages,
|
||||
// ... other parameters
|
||||
metadata: buildApiRequestMetadata()
|
||||
});
|
||||
```
|
||||
|
||||
### 3. Tree Shaking for Internal Builds
|
||||
|
||||
The feature should be conditionally compiled out for public builds using build-time flags:
|
||||
|
||||
```typescript
|
||||
// Using a build-time constant
|
||||
declare const __ANT_INTERNAL_BUILD__: boolean;
|
||||
|
||||
export function isAnthropicBuild(): boolean {
|
||||
// This will be replaced at build time
|
||||
// For internal builds: true
|
||||
// For public builds: false (and the code will be tree-shaken)
|
||||
if (typeof __ANT_INTERNAL_BUILD__ !== 'undefined') {
|
||||
return __ANT_INTERNAL_BUILD__;
|
||||
}
|
||||
return false;
|
||||
}
|
||||
```
|
||||
|
||||
In the build configuration (esbuild/webpack/rollup):
|
||||
|
||||
```javascript
|
||||
// For public builds:
|
||||
define: {
|
||||
'__ANT_INTERNAL_BUILD__': 'false'
|
||||
}
|
||||
|
||||
// For internal builds:
|
||||
define: {
|
||||
'__ANT_INTERNAL_BUILD__': 'true'
|
||||
}
|
||||
```
|
||||
|
||||
### 4. Validation (Optional but Recommended)
|
||||
|
||||
```typescript
|
||||
function validateMetadataUserId(value: string): boolean {
|
||||
try {
|
||||
const parsed = JSON.parse(value);
|
||||
return typeof parsed.user === 'string' && typeof parsed.job === 'string';
|
||||
} catch {
|
||||
// Also allow simple string format for backward compatibility
|
||||
return typeof value === 'string' && value.length > 0;
|
||||
}
|
||||
}
|
||||
|
||||
export function getValidatedAntOnlyMetadataUserId(): string | undefined {
|
||||
const value = getAntOnlyMetadataUserId();
|
||||
if (value && !validateMetadataUserId(value)) {
|
||||
console.warn('ANT_ONLY_METADATA_USER_ID has invalid format. Expected JSON: {"user": "...", "job": "..."}');
|
||||
return undefined;
|
||||
}
|
||||
return value;
|
||||
}
|
||||
```
|
||||
|
||||
## Usage by Internal Services
|
||||
|
||||
Services like Claude Oracle should set this environment variable before launching Claude Code sessions:
|
||||
|
||||
```python
|
||||
# In Claude Oracle / coo job code
|
||||
import os
|
||||
import json
|
||||
|
||||
# Set the metadata before spawning Claude Code
|
||||
os.environ['ANT_ONLY_METADATA_USER_ID'] = json.dumps({
|
||||
"user": username, # Anthropic username
|
||||
"job": job_name # e.g., "claude-oracle:fluorine:vinke"
|
||||
})
|
||||
|
||||
# Then launch Claude Code session...
|
||||
```
|
||||
|
||||
Or via command line:
|
||||
|
||||
```bash
|
||||
ANT_ONLY_METADATA_USER_ID='{"user":"tedm","job":"tedm-1208-mu-g-18x"}' claude --headless ...
|
||||
```
|
||||
|
||||
## Data Flow
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ COO Job / Oracle / Oncall / etc. │
|
||||
│ Sets: ANT_ONLY_METADATA_USER_ID='{"user":"..","job":".."}' │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
│
|
||||
▼
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ Claude Code CLI │
|
||||
│ Reads: process.env.ANT_ONLY_METADATA_USER_ID │
|
||||
│ Adds to API calls: metadata: { user_id: "..." } │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
│
|
||||
▼
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ Anthropic API │
|
||||
│ Receives: metadata.user_id in request │
|
||||
│ Stores in: api_usage.metadata_user_id (BigQuery) │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
│
|
||||
▼
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ BigQuery: anthropic.api_production.api_usage │
|
||||
│ Fields populated: │
|
||||
│ - metadata_user_id │
|
||||
│ - device_id (if included) │
|
||||
│ - claude_code_session_id (if included) │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
## Testing
|
||||
|
||||
1. **Unit Tests**:
|
||||
- Test that `getAntOnlyMetadataUserId()` returns undefined when env var is not set
|
||||
- Test that it returns the value when set (in internal builds)
|
||||
- Test validation of JSON format
|
||||
|
||||
2. **Integration Tests**:
|
||||
- Verify metadata is included in API requests
|
||||
- Verify tree-shaking removes the code in public builds
|
||||
|
||||
3. **E2E Validation** (after deployment):
|
||||
- Run a Claude Code session with the env var set
|
||||
- Query BigQuery `anthropic.api_production.api_usage` to verify `metadata_user_id` is populated
|
||||
|
||||
## Security Considerations
|
||||
|
||||
1. **Internal Only**: The tree-shaking ensures this feature is not available in public builds
|
||||
2. **No Secrets**: The metadata should not contain sensitive information
|
||||
3. **Validation**: Input validation prevents injection attacks
|
||||
|
||||
## Related Files to Modify (Internal Repo)
|
||||
|
||||
Based on patterns in the bundled CLI, likely files to modify:
|
||||
|
||||
1. `src/config/env.ts` or similar - Add env var reading
|
||||
2. `src/api/anthropic.ts` or similar - Add metadata to API requests
|
||||
3. `build.config.ts` or similar - Add build-time flag for internal builds
|
||||
4. Tests for the above
|
||||
|
||||
## References
|
||||
|
||||
- Slack thread: Internal API metadata discussion
|
||||
- BigQuery tables: `anthropic.api_production.api_usage`, `api_events`
|
||||
- Anthropic API docs: [Messages API metadata parameter](https://docs.anthropic.com/en/api/messages)
|
||||
238
CHANGELOG.md
238
CHANGELOG.md
@@ -1,5 +1,243 @@
|
||||
# Changelog
|
||||
|
||||
## 2.1.2
|
||||
|
||||
- Added source path metadata to images dragged onto the terminal, helping Claude understand where images originated
|
||||
- Added clickable hyperlinks for file paths in tool output in terminals that support OSC 8 (like iTerm)
|
||||
- Added support for Windows Package Manager (winget) installations with automatic detection and update instructions
|
||||
- Added Shift+Tab keyboard shortcut in plan mode to quickly select "auto-accept edits" option
|
||||
- Added `FORCE_AUTOUPDATE_PLUGINS` environment variable to allow plugin autoupdate even when the main auto-updater is disabled
|
||||
- Added `agent_type` to SessionStart hook input, populated if `--agent` is specified
|
||||
- Fixed a command injection vulnerability in bash command processing where malformed input could execute arbitrary commands
|
||||
- Fixed a memory leak where tree-sitter parse trees were not being freed, causing WASM memory to grow unbounded over long sessions
|
||||
- Fixed binary files (images, PDFs, etc.) being accidentally included in memory when using `@include` directives in CLAUDE.md files
|
||||
- Fixed updates incorrectly claiming another installation is in progress
|
||||
- Fixed crash when socket files exist in watched directories (defense-in-depth for EOPNOTSUPP errors)
|
||||
- Fixed remote session URL and teleport being broken when using `/tasks` command
|
||||
- Fixed MCP tool names being exposed in analytics events by sanitizing user-specific server configurations
|
||||
- Improved Option-as-Meta hint on macOS to show terminal-specific instructions for native CSIu terminals like iTerm2, Kitty, and WezTerm
|
||||
- Improved error message when pasting images over SSH to suggest using `scp` instead of the unhelpful clipboard shortcut hint
|
||||
- Improved permission explainer to not flag routine dev workflows (git fetch/rebase, npm install, tests, PRs) as medium risk
|
||||
- Changed large bash command outputs to be saved to disk instead of truncated, allowing Claude to read the full content
|
||||
- Changed large tool outputs to be persisted to disk instead of truncated, providing full output access via file references
|
||||
- Changed `/plugins` installed tab to unify plugins and MCPs with scope-based grouping
|
||||
- Deprecated Windows managed settings path `C:\ProgramData\ClaudeCode\managed-settings.json` - administrators should migrate to `C:\Program Files\ClaudeCode\managed-settings.json`
|
||||
- [SDK] Changed minimum zod peer dependency to ^4.0.0
|
||||
- [VSCode] Fixed usage display not updating after manual compact
|
||||
|
||||
## 2.1.0
|
||||
|
||||
- Added automatic skill hot-reload - skills created or modified in `~/.claude/skills` or `.claude/skills` are now immediately available without restarting the session
|
||||
- Added support for running skills and slash commands in a forked sub-agent context using `context: fork` in skill frontmatter
|
||||
- Added support for `agent` field in skills to specify agent type for execution
|
||||
- Added `language` setting to configure Claude's response language (e.g., language: "japanese")
|
||||
- Changed Shift+Enter to work out of the box in iTerm2, WezTerm, Ghostty, and Kitty without modifying terminal configs
|
||||
- Added `respectGitignore` support in `settings.json` for per-project control over @-mention file picker behavior
|
||||
- Added `IS_DEMO` environment variable to hide email and organization from the UI, useful for streaming or recording sessions
|
||||
- Fixed security issue where sensitive data (OAuth tokens, API keys, passwords) could be exposed in debug logs
|
||||
- Fixed files and skills not being properly discovered when resuming sessions with `-c` or `--resume`
|
||||
- Fixed pasted content being lost when replaying prompts from history using up arrow or Ctrl+R search
|
||||
- Fixed Esc key with queued prompts to only move them to input without canceling the running task
|
||||
- Reduced permission prompts for complex bash commands
|
||||
- Fixed command search to prioritize exact and prefix matches on command names over fuzzy matches in descriptions
|
||||
- Fixed PreToolUse hooks to allow `updatedInput` when returning `ask` permission decision, enabling hooks to act as middleware while still requesting user consent
|
||||
- Fixed plugin path resolution for file-based marketplace sources
|
||||
- Fixed LSP tool being incorrectly enabled when no LSP servers were configured
|
||||
- Fixed background tasks failing with "git repository not found" error for repositories with dots in their names
|
||||
- Fixed Claude in Chrome support for WSL environments
|
||||
- Fixed Windows native installer silently failing when executable creation fails
|
||||
- Improved CLI help output to display options and subcommands in alphabetical order for easier navigation
|
||||
- Added wildcard pattern matching for Bash tool permissions using `*` at any position in rules (e.g., `Bash(npm *)`, `Bash(* install)`, `Bash(git * main)`)
|
||||
- Added unified Ctrl+B backgrounding for both bash commands and agents - pressing Ctrl+B now backgrounds all running foreground tasks simultaneously
|
||||
- Added support for MCP `list_changed` notifications, allowing MCP servers to dynamically update their available tools, prompts, and resources without requiring reconnection
|
||||
- Added `/teleport` and `/remote-env` slash commands for claude.ai subscribers, allowing them to resume and configure remote sessions
|
||||
- Added support for disabling specific agents using `Task(AgentName)` syntax in settings.json permissions or the `--disallowedTools` CLI flag
|
||||
- Added hooks support to agent frontmatter, allowing agents to define PreToolUse, PostToolUse, and Stop hooks scoped to the agent's lifecycle
|
||||
- Added hooks support for skill and slash command frontmatter
|
||||
- Added new Vim motions: `;` and `,` to repeat f/F/t/T motions, `y` operator for yank with `yy`/`Y`, `p`/`P` for paste, text objects (`iw`, `aw`, `iW`, `aW`, `i"`, `a"`, `i'`, `a'`, `i(`, `a(`, `i[`, `a[`, `i{`, `a{`), `>>` and `<<` for indent/dedent, and `J` to join lines
|
||||
- Added `/plan` command shortcut to enable plan mode directly from the prompt
|
||||
- Added slash command autocomplete support when `/` appears anywhere in input, not just at the beginning
|
||||
- Added `--tools` flag support in interactive mode to restrict which built-in tools Claude can use during interactive sessions
|
||||
- Added `CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS` environment variable to override the default file read token limit
|
||||
- Added support for `once: true` config for hooks
|
||||
- Added support for YAML-style lists in frontmatter `allowed-tools` field for cleaner skill declarations
|
||||
- Added support for prompt and agent hook types from plugins (previously only command hooks were supported)
|
||||
- Added Cmd+V support for image paste in iTerm2 (maps to Ctrl+V)
|
||||
- Added left/right arrow key navigation for cycling through tabs in dialogs
|
||||
- Added real-time thinking block display in Ctrl+O transcript mode
|
||||
- Added filepath to full output in background bash task details dialog
|
||||
- Added Skills as a separate category in the context visualization
|
||||
- Fixed OAuth token refresh not triggering when server reports token expired but local expiration check disagrees
|
||||
- Fixed session persistence getting stuck after transient server errors by recovering from 409 conflicts when the entry was actually stored
|
||||
- Fixed session resume failures caused by orphaned tool results during concurrent tool execution
|
||||
- Fixed a race condition where stale OAuth tokens could be read from the keychain cache during concurrent token refresh attempts
|
||||
- Fixed AWS Bedrock subagents not inheriting EU/APAC cross-region inference model configuration, causing 403 errors when IAM permissions are scoped to specific regions
|
||||
- Fixed API context overflow when background tasks produce large output by truncating to 30K chars with file path reference
|
||||
- Fixed a hang when reading FIFO files by skipping symlink resolution for special file types
|
||||
- Fixed terminal keyboard mode not being reset on exit in Ghostty, iTerm2, Kitty, and WezTerm
|
||||
- Fixed Alt+B and Alt+F (word navigation) not working in iTerm2, Ghostty, Kitty, and WezTerm
|
||||
- Fixed `${CLAUDE_PLUGIN_ROOT}` not being substituted in plugin `allowed-tools` frontmatter, which caused tools to incorrectly require approval
|
||||
- Fixed files created by the Write tool using hardcoded 0o600 permissions instead of respecting the system umask
|
||||
- Fixed commands with `$()` command substitution failing with parse errors
|
||||
- Fixed multi-line bash commands with backslash continuations being incorrectly split and flagged for permissions
|
||||
- Fixed bash command prefix extraction to correctly identify subcommands after global options (e.g., `git -C /path log` now correctly matches `Bash(git log:*)` rules)
|
||||
- Fixed slash commands passed as CLI arguments (e.g., `claude /context`) not being executed properly
|
||||
- Fixed pressing Enter after Tab-completing a slash command selecting a different command instead of submitting the completed one
|
||||
- Fixed slash command argument hint flickering and inconsistent display when typing commands with arguments
|
||||
- Fixed Claude sometimes redundantly invoking the Skill tool when running slash commands directly
|
||||
- Fixed skill token estimates in `/context` to accurately reflect frontmatter-only loading
|
||||
- Fixed subagents sometimes not inheriting the parent's model by default
|
||||
- Fixed model picker showing incorrect selection for Bedrock/Vertex users using `--model haiku`
|
||||
- Fixed duplicate Bash commands appearing in permission request option labels
|
||||
- Fixed noisy output when background tasks complete - now shows clean completion message instead of raw output
|
||||
- Fixed background task completion notifications to appear proactively with bullet point
|
||||
- Fixed forked slash commands showing "AbortError" instead of "Interrupted" message when cancelled
|
||||
- Fixed cursor disappearing after dismissing permission dialogs
|
||||
- Fixed `/hooks` menu selecting wrong hook type when scrolling to a different option
|
||||
- Fixed images in queued prompts showing as "[object Object]" when pressing Esc to cancel
|
||||
- Fixed images being silently dropped when queueing messages while backgrounding a task
|
||||
- Fixed large pasted images failing with "Image was too large" error
|
||||
- Fixed extra blank lines in multiline prompts containing CJK characters (Japanese, Chinese, Korean)
|
||||
- Fixed ultrathink keyword highlighting being applied to wrong characters when user prompt text wraps to multiple lines
|
||||
- Fixed collapsed "Reading X files…" indicator incorrectly switching to past tense when thinking blocks appear mid-stream
|
||||
- Fixed Bash read commands (like `ls` and `cat`) not being counted in collapsed read/search groups, causing groups to incorrectly show "Read 0 files"
|
||||
- Fixed spinner token counter to properly accumulate tokens from subagents during execution
|
||||
- Fixed memory leak in git diff parsing where sliced strings retained large parent strings
|
||||
- Fixed race condition where LSP tool could return "no server available" during startup
|
||||
- Fixed feedback submission hanging indefinitely when network requests timeout
|
||||
- Fixed search mode in plugin discovery and log selector views exiting when pressing up arrow
|
||||
- Fixed hook success message showing trailing colon when hook has no output
|
||||
- Multiple optimizations to improve startup performance
|
||||
- Improved terminal rendering performance when using native installer or Bun, especially for text with emoji, ANSI codes, and Unicode characters
|
||||
- Improved performance when reading Jupyter notebooks with many cells
|
||||
- Improved reliability for piped input like `cat refactor.md | claude`
|
||||
- Improved reliability for AskQuestion tool
|
||||
- Improved sed in-place edit commands to render as file edits with diff preview
|
||||
- Improved Claude to automatically continue when response is cut off due to output token limit, instead of showing an error message
|
||||
- Improved compaction reliability
|
||||
- Improved subagents (Task tool) to continue working after permission denial, allowing them to try alternative approaches
|
||||
- Improved skills to show progress while executing, displaying tool uses as they happen
|
||||
- Improved skills from `/skills/` directories to be visible in the slash command menu by default (opt-out with `user-invocable: false` in frontmatter)
|
||||
- Improved skill suggestions to prioritize recently and frequently used skills
|
||||
- Improved spinner feedback when waiting for the first response token
|
||||
- Improved token count display in spinner to include tokens from background agents
|
||||
- Improved incremental output for async agents to give the main thread more control and visibility
|
||||
- Improved permission prompt UX with Tab hint moved to footer, cleaner Yes/No input labels with contextual placeholders
|
||||
- Improved the Claude in Chrome notification with shortened help text and persistent display until dismissed
|
||||
- Improved macOS screenshot paste reliability with TIFF format support
|
||||
- Improved `/stats` output
|
||||
- Updated Atlassian MCP integration to use a more reliable default configuration (streamable HTTP)
|
||||
- Changed "Interrupted" message color from red to grey for a less alarming appearance
|
||||
- Removed permission prompt when entering plan mode - users can now enter plan mode without approval
|
||||
- Removed underline styling from image reference links
|
||||
- [SDK] Changed minimum zod peer dependency to ^4.0.0
|
||||
- [VSCode] Added currently selected model name to the context menu
|
||||
- [VSCode] Added descriptive labels on auto-accept permission button (e.g., "Yes, allow npm for this project" instead of "Yes, and don't ask again")
|
||||
- [VSCode] Fixed paragraph breaks not rendering in markdown content
|
||||
- [VSCode] Fixed scrolling in the extension inadvertently scrolling the parent iframe
|
||||
- [Windows] Fixed issue with improper rendering
|
||||
|
||||
## 2.0.76
|
||||
|
||||
- Fixed issue with macOS code-sign warning when using Claude in Chrome integration
|
||||
|
||||
## 2.0.75
|
||||
|
||||
- Minor bugfixes
|
||||
|
||||
## 2.0.74
|
||||
|
||||
- Added LSP (Language Server Protocol) tool for code intelligence features like go-to-definition, find references, and hover documentation
|
||||
- Added `/terminal-setup` support for Kitty, Alacritty, Zed, and Warp terminals
|
||||
- Added ctrl+t shortcut in `/theme` to toggle syntax highlighting on/off
|
||||
- Added syntax highlighting info to theme picker
|
||||
- Added guidance for macOS users when Alt shortcuts fail due to terminal configuration
|
||||
- Fixed skill `allowed-tools` not being applied to tools invoked by the skill
|
||||
- Fixed Opus 4.5 tip incorrectly showing when user was already using Opus
|
||||
- Fixed a potential crash when syntax highlighting isn't initialized correctly
|
||||
- Fixed visual bug in `/plugins discover` where list selection indicator showed while search box was focused
|
||||
- Fixed macOS keyboard shortcuts to display 'opt' instead of 'alt'
|
||||
- Improved `/context` command visualization with grouped skills and agents by source, slash commands, and sorted token count
|
||||
- [Windows] Fixed issue with improper rendering
|
||||
- [VSCode] Added gift tag pictogram for year-end promotion message
|
||||
|
||||
## 2.0.73
|
||||
|
||||
- Added clickable `[Image #N]` links that open attached images in the default viewer
|
||||
- Added alt-y yank-pop to cycle through kill ring history after ctrl-y yank
|
||||
- Added search filtering to the plugin discover screen (type to filter by name, description, or marketplace)
|
||||
- Added support for custom session IDs when forking sessions with `--session-id` combined with `--resume` or `--continue` and `--fork-session`
|
||||
- Fixed slow input history cycling and race condition that could overwrite text after message submission
|
||||
- Improved `/theme` command to open theme picker directly
|
||||
- Improved theme picker UI
|
||||
- Improved search UX across resume session, permissions, and plugins screens with a unified SearchBox component
|
||||
- [VSCode] Added tab icon badges showing pending permissions (blue) and unread completions (orange)
|
||||
|
||||
## 2.0.72
|
||||
|
||||
- Added Claude in Chrome (Beta) feature that works with the Chrome extension (https://claude.ai/chrome) to let you control your browser directly from Claude Code
|
||||
- Reduced terminal flickering
|
||||
- Added scannable QR code to mobile app tip for quick app downloads
|
||||
- Added loading indicator when resuming conversations for better feedback
|
||||
- Fixed `/context` command not respecting custom system prompts in non-interactive mode
|
||||
- Fixed order of consecutive Ctrl+K lines when pasting with Ctrl+Y
|
||||
- Improved @ mention file suggestion speed (~3x faster in git repositories)
|
||||
- Improved file suggestion performance in repos with `.ignore` or `.rgignore` files
|
||||
- Improved settings validation errors to be more prominent
|
||||
- Changed thinking toggle from Tab to Alt+T to avoid accidental triggers
|
||||
|
||||
## 2.0.71
|
||||
|
||||
- Added /config toggle to enable/disable prompt suggestions
|
||||
- Added `/settings` as an alias for the `/config` command
|
||||
- Fixed @ file reference suggestions incorrectly triggering when cursor is in the middle of a path
|
||||
- Fixed MCP servers from `.mcp.json` not loading when using `--dangerously-skip-permissions`
|
||||
- Fixed permission rules incorrectly rejecting valid bash commands containing shell glob patterns (e.g., `ls *.txt`, `for f in *.png`)
|
||||
- Bedrock: Environment variable `ANTHROPIC_BEDROCK_BASE_URL` is now respected for token counting and inference profile listing
|
||||
- New syntax highlighting engine for native build
|
||||
|
||||
## 2.0.70
|
||||
|
||||
- Added Enter key to accept and submit prompt suggestions immediately (tab still accepts for editing)
|
||||
- Added wildcard syntax `mcp__server__*` for MCP tool permissions to allow or deny all tools from a server
|
||||
- Added auto-update toggle for plugin marketplaces, allowing per-marketplace control over automatic updates
|
||||
- Added `current_usage` field to status line input, enabling accurate context window percentage calculations
|
||||
- Fixed input being cleared when processing queued commands while the user was typing
|
||||
- Fixed prompt suggestions replacing typed input when pressing Tab
|
||||
- Fixed diff view not updating when terminal is resized
|
||||
- Improved memory usage by 3x for large conversations
|
||||
- Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images
|
||||
- Removed # shortcut for quick memory entry (tell Claude to edit your CLAUDE.md instead)
|
||||
- Fix thinking mode toggle in /config not persisting correctly
|
||||
- Improve UI for file creation permission dialog
|
||||
|
||||
## 2.0.69
|
||||
|
||||
- Minor bugfixes
|
||||
|
||||
## 2.0.68
|
||||
|
||||
- Fixed IME (Input Method Editor) support for languages like Chinese, Japanese, and Korean by correctly positioning the composition window at the cursor
|
||||
- Fixed a bug where disallowed MCP tools were visible to the model
|
||||
- Fixed an issue where steering messages could be lost while a subagent is working
|
||||
- Fixed Option+Arrow word navigation treating entire CJK (Chinese, Japanese, Korean) text sequences as a single word instead of navigating by word boundaries
|
||||
- Improved plan mode exit UX: show simplified yes/no dialog when exiting with empty or missing plan instead of throwing an error
|
||||
- Add support for enterprise managed settings. Contact your Anthropic account team to enable this feature.
|
||||
|
||||
## 2.0.67
|
||||
|
||||
- Thinking mode is now enabled by default for Opus 4.5
|
||||
- Thinking mode configuration has moved to /config
|
||||
- Added search functionality to `/permissions` command with `/` keyboard shortcut for filtering rules by tool name
|
||||
- Show reason why autoupdater is disabled in `/doctor`
|
||||
- Fixed false "Another process is currently updating Claude" error when running `claude update` while another instance is already on the latest version
|
||||
- Fixed MCP servers from `.mcp.json` being stuck in pending state when running in non-interactive mode (`-p` flag or piped input)
|
||||
- Fixed scroll position resetting after deleting a permission rule in `/permissions`
|
||||
- Fixed word deletion (opt+delete) and word navigation (opt+arrow) not working correctly with non-Latin text such as Cyrillic, Greek, Arabic, Hebrew, Thai, and Chinese
|
||||
- Fixed `claude install --force` not bypassing stale lock files
|
||||
- Fixed consecutive @~/ file references in CLAUDE.md being incorrectly parsed due to markdown strikethrough interference
|
||||
- Windows: Fixed plugin MCP servers failing due to colons in log directory paths
|
||||
|
||||
## 2.0.65
|
||||
|
||||
- Added ability to switch models while writing a prompt using alt+p (linux, windows), option+p (macos).
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
|
||||
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language commands. Use it in your terminal, IDE, or tag @claude on Github.
|
||||
|
||||
**Learn more in the [official documentation](https://docs.anthropic.com/en/docs/claude-code/overview)**.
|
||||
**Learn more in the [official documentation](https://code.claude.com/docs/en/overview)**.
|
||||
|
||||
<img src="./demo.gif" />
|
||||
|
||||
@@ -56,7 +56,7 @@ When you use Claude Code, we collect feedback, which includes usage data (such a
|
||||
|
||||
### How we use your data
|
||||
|
||||
See our [data usage policies](https://docs.anthropic.com/en/docs/claude-code/data-usage).
|
||||
See our [data usage policies](https://code.claude.com/docs/en/data-usage).
|
||||
|
||||
### Privacy safeguards
|
||||
|
||||
|
||||
@@ -22,23 +22,29 @@ Performs automated code review on a pull request using multiple specialized agen
|
||||
- **Agent #4**: Analyze git blame/history for context-based issues
|
||||
5. Scores each issue 0-100 for confidence level
|
||||
6. Filters out issues below 80 confidence threshold
|
||||
7. Posts review comment with high-confidence issues only
|
||||
7. Outputs review (to terminal by default, or as PR comment with `--comment` flag)
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
/code-review
|
||||
/code-review [--comment]
|
||||
```
|
||||
|
||||
**Options:**
|
||||
- `--comment`: Post the review as a comment on the pull request (default: outputs to terminal only)
|
||||
|
||||
**Example workflow:**
|
||||
```bash
|
||||
# On a PR branch, run:
|
||||
# On a PR branch, run locally (outputs to terminal):
|
||||
/code-review
|
||||
|
||||
# Post review as PR comment:
|
||||
/code-review --comment
|
||||
|
||||
# Claude will:
|
||||
# - Launch 4 review agents in parallel
|
||||
# - Score each issue for confidence
|
||||
# - Post comment with issues ≥80 confidence
|
||||
# - Skip posting if no high-confidence issues found
|
||||
# - Output issues ≥80 confidence (to terminal or PR depending on flag)
|
||||
# - Skip if no high-confidence issues found
|
||||
```
|
||||
|
||||
**Features:**
|
||||
@@ -114,17 +120,23 @@ This plugin is included in the Claude Code repository. The command is automatica
|
||||
### Standard PR review workflow:
|
||||
```bash
|
||||
# Create PR with changes
|
||||
# Run local review (outputs to terminal)
|
||||
/code-review
|
||||
|
||||
# Review the automated feedback
|
||||
# Make any necessary fixes
|
||||
|
||||
# Optionally post as PR comment
|
||||
/code-review --comment
|
||||
|
||||
# Merge when ready
|
||||
```
|
||||
|
||||
### As part of CI/CD:
|
||||
```bash
|
||||
# Trigger on PR creation or update
|
||||
# Automatically posts review comments
|
||||
# Use --comment flag to post review comments
|
||||
/code-review --comment
|
||||
# Skip if review already exists
|
||||
```
|
||||
|
||||
|
||||
@@ -1,17 +1,21 @@
|
||||
---
|
||||
allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*), Bash(gh pr list:*)
|
||||
allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*), Bash(gh pr list:*), mcp__github_inline_comment__create_inline_comment
|
||||
description: Code review a pull request
|
||||
---
|
||||
|
||||
Provide a code review for the given pull request.
|
||||
|
||||
**Agent assumptions (applies to all agents and subagents):**
|
||||
- All tools are functional and will work without error. Do not test tools or make exploratory calls.
|
||||
- Only call a tool if it is required to complete the task. Every tool call should have a clear purpose.
|
||||
|
||||
To do this, follow these steps precisely:
|
||||
|
||||
1. Launch a haiku agent to check if any of the following are true:
|
||||
- The pull request is closed
|
||||
- The pull request is a draft
|
||||
- The pull request does not need code review (e.g. automated PR, trivial change that is obviously correct)
|
||||
- You have already submitted a code review on this pull request
|
||||
- Claude has already commented on this PR (check `gh pr view <PR> --comments` for comments left by claude)
|
||||
|
||||
If any condition is true, stop and do not proceed.
|
||||
|
||||
@@ -34,15 +38,15 @@ Note: Still review Claude generated PR's.
|
||||
Agent 4: Opus bug agent (parallel subagent with agent 3)
|
||||
Look for problems that exist in the introduced code. This could be security issues, incorrect logic, etc. Only look for issues that fall within the changed code.
|
||||
|
||||
**CRITICAL: We only want HIGH SIGNAL issues.** This means:
|
||||
- Objective bugs that will cause incorrect behavior at runtime
|
||||
**CRITICAL: We only want HIGH SIGNAL issues.** Flag issues where:
|
||||
- The code will fail to compile or parse (syntax errors, type errors, missing imports, unresolved references)
|
||||
- The code will definitely produce wrong results regardless of inputs (clear logic errors)
|
||||
- Clear, unambiguous CLAUDE.md violations where you can quote the exact rule being broken
|
||||
|
||||
We do NOT want:
|
||||
- Subjective concerns or "suggestions"
|
||||
- Style preferences not explicitly required by CLAUDE.md
|
||||
- Potential issues that "might" be problems
|
||||
- Anything requiring interpretation or judgment calls
|
||||
Do NOT flag:
|
||||
- Code style or quality concerns
|
||||
- Potential issues that depend on specific inputs or state
|
||||
- Subjective suggestions or improvements
|
||||
|
||||
If you are not certain an issue is real, do not flag it. False positives erode trust and waste reviewer time.
|
||||
|
||||
@@ -52,12 +56,17 @@ Note: Still review Claude generated PR's.
|
||||
|
||||
6. Filter out any issues that were not validated in step 5. This step will give us our list of high signal issues for our review.
|
||||
|
||||
7. Finally, comment on the pull request.
|
||||
When writing your comment, follow these guidelines:
|
||||
a. Keep your output brief
|
||||
b. Avoid emojis
|
||||
c. Link and cite relevant code, files, and URLs for each issue
|
||||
d. When citing CLAUDE.md violations, you MUST quote the exact text from CLAUDE.md that is being violated (e.g., CLAUDE.md says: "Use snake_case for variable names")
|
||||
7. If issues were found, skip to step 8 to post inline comments directly.
|
||||
|
||||
If NO issues were found, post a summary comment using `gh pr comment` (if `--comment` argument is provided):
|
||||
"No issues found. Checked for bugs and CLAUDE.md compliance."
|
||||
|
||||
8. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`. For each comment:
|
||||
- Provide a brief description of the issue
|
||||
- For small, self-contained fixes, include a committable suggestion block
|
||||
- For larger fixes (6+ lines, structural changes, or changes spanning multiple locations), describe the issue and suggested fix without a suggestion block
|
||||
|
||||
**IMPORTANT: Only post ONE comment per unique issue. Do not post duplicate comments.**
|
||||
|
||||
Use this list when evaluating issues in Steps 4 and 5 (these are false positives, do NOT flag):
|
||||
|
||||
@@ -72,47 +81,18 @@ Notes:
|
||||
|
||||
- Use gh CLI to interact with GitHub (e.g., fetch pull requests, create comments). Do not use web fetch.
|
||||
- Create a todo list before starting.
|
||||
- You must cite and link each issue (e.g., if referring to a CLAUDE.md, include a link to it).
|
||||
- For your final comment, follow the following format precisely (assuming for this example that you found 3 issues):
|
||||
- You must cite and link each issue in inline comments (e.g., if referring to a CLAUDE.md, include a link to it).
|
||||
- If no issues are found, post a comment with the following format:
|
||||
|
||||
---
|
||||
|
||||
## Code review
|
||||
|
||||
Found 3 issues:
|
||||
|
||||
1. <brief description of bug> (CLAUDE.md says: "<exact quote from CLAUDE.md>")
|
||||
|
||||
<link to file and line with full sha1 + line range for context, eg. https://github.com/anthropics/claude-code/blob/1d54823877c4de72b2316a64032a54afc404e619/README.md#L13-L17>
|
||||
|
||||
2. <brief description of bug> (some/other/CLAUDE.md says: "<exact quote from CLAUDE.md>")
|
||||
|
||||
<link to file and line with full sha1 + line range for context>
|
||||
|
||||
3. <brief description of bug> (bug due to <file and code snippet>)
|
||||
|
||||
<link to file and line with full sha1 + line range for context>
|
||||
|
||||
🤖 Generated with [Claude Code](https://claude.ai/code)
|
||||
|
||||
|
||||
<sub>- If this code review was useful, please react with 👍. Otherwise, react with 👎.</sub>
|
||||
|
||||
---
|
||||
|
||||
- Or, if you found no issues:
|
||||
|
||||
---
|
||||
|
||||
## Auto code review
|
||||
|
||||
No issues found. Checked for bugs and CLAUDE.md compliance.
|
||||
|
||||
🤖 Generated with [Claude Code](https://claude.ai/code)
|
||||
|
||||
---
|
||||
|
||||
- When linking to code, follow the following format precisely, otherwise the Markdown preview won't render correctly: https://github.com/anthropics/claude-code/blob/c21d3c10bc8e898b7ac1a2d745bdc9bc4e423afe/package.json#L10-L15
|
||||
- When linking to code in inline comments, follow the following format precisely, otherwise the Markdown preview won't render correctly: https://github.com/anthropics/claude-code/blob/c21d3c10bc8e898b7ac1a2d745bdc9bc4e423afe/package.json#L10-L15
|
||||
- Requires full git sha
|
||||
- You must provide the full sha. Commands like `https://github.com/owner/repo/blob/$(git rev-parse HEAD)/foo/bar` will not work, since your comment will be directly rendered in Markdown.
|
||||
- Repo name must match the repo you're code reviewing
|
||||
|
||||
@@ -1,26 +1,18 @@
|
||||
---
|
||||
description: "Cancel active Ralph Wiggum loop"
|
||||
allowed-tools: ["Bash"]
|
||||
allowed-tools: ["Bash(test -f .claude/ralph-loop.local.md:*)", "Bash(rm .claude/ralph-loop.local.md)", "Read(.claude/ralph-loop.local.md)"]
|
||||
hide-from-slash-command-tool: "true"
|
||||
---
|
||||
|
||||
# Cancel Ralph
|
||||
|
||||
```!
|
||||
if [[ -f .claude/ralph-loop.local.md ]]; then
|
||||
ITERATION=$(grep '^iteration:' .claude/ralph-loop.local.md | sed 's/iteration: *//')
|
||||
echo "FOUND_LOOP=true"
|
||||
echo "ITERATION=$ITERATION"
|
||||
else
|
||||
echo "FOUND_LOOP=false"
|
||||
fi
|
||||
```
|
||||
To cancel the Ralph loop:
|
||||
|
||||
Check the output above:
|
||||
1. Check if `.claude/ralph-loop.local.md` exists using Bash: `test -f .claude/ralph-loop.local.md && echo "EXISTS" || echo "NOT_FOUND"`
|
||||
|
||||
1. **If FOUND_LOOP=false**:
|
||||
- Say "No active Ralph loop found."
|
||||
2. **If NOT_FOUND**: Say "No active Ralph loop found."
|
||||
|
||||
2. **If FOUND_LOOP=true**:
|
||||
- Use Bash: `rm .claude/ralph-loop.local.md`
|
||||
- Report: "Cancelled Ralph loop (was at iteration N)" where N is the ITERATION value from above.
|
||||
3. **If EXISTS**:
|
||||
- Read `.claude/ralph-loop.local.md` to get the current iteration number from the `iteration:` field
|
||||
- Remove the file using Bash: `rm .claude/ralph-loop.local.md`
|
||||
- Report: "Cancelled Ralph loop (was at iteration N)" where N is the iteration value
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
description: "Start Ralph Wiggum loop in current session"
|
||||
argument-hint: "PROMPT [--max-iterations N] [--completion-promise TEXT]"
|
||||
allowed-tools: ["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh)"]
|
||||
allowed-tools: ["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh:*)"]
|
||||
hide-from-slash-command-tool: "true"
|
||||
---
|
||||
|
||||
@@ -11,36 +11,6 @@ Execute the setup script to initialize the Ralph loop:
|
||||
|
||||
```!
|
||||
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh" $ARGUMENTS
|
||||
|
||||
# Extract and display completion promise if set
|
||||
if [ -f .claude/ralph-loop.local.md ]; then
|
||||
PROMISE=$(grep '^completion_promise:' .claude/ralph-loop.local.md | sed 's/completion_promise: *//' | sed 's/^"\(.*\)"$/\1/')
|
||||
if [ -n "$PROMISE" ] && [ "$PROMISE" != "null" ]; then
|
||||
echo ""
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
echo "CRITICAL - Ralph Loop Completion Promise"
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
echo ""
|
||||
echo "To complete this loop, output this EXACT text:"
|
||||
echo " <promise>$PROMISE</promise>"
|
||||
echo ""
|
||||
echo "STRICT REQUIREMENTS (DO NOT VIOLATE):"
|
||||
echo " ✓ Use <promise> XML tags EXACTLY as shown above"
|
||||
echo " ✓ The statement MUST be completely and unequivocally TRUE"
|
||||
echo " ✓ Do NOT output false statements to exit the loop"
|
||||
echo " ✓ Do NOT lie even if you think you should exit"
|
||||
echo ""
|
||||
echo "IMPORTANT - Do not circumvent the loop:"
|
||||
echo " Even if you believe you're stuck, the task is impossible,"
|
||||
echo " or you've been running too long - you MUST NOT output a"
|
||||
echo " false promise statement. The loop is designed to continue"
|
||||
echo " until the promise is GENUINELY TRUE. Trust the process."
|
||||
echo ""
|
||||
echo " If the loop should stop, the promise statement will become"
|
||||
echo " true naturally. Do not force it by lying."
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
fi
|
||||
fi
|
||||
```
|
||||
|
||||
Please work on the task. When you try to exit, the Ralph loop will feed the SAME PROMPT back to you for the next iteration. You'll see your previous work in files and git history, allowing you to iterate and improve.
|
||||
|
||||
@@ -174,3 +174,30 @@ if [[ -n "$PROMPT" ]]; then
|
||||
echo ""
|
||||
echo "$PROMPT"
|
||||
fi
|
||||
|
||||
# Display completion promise requirements if set
|
||||
if [[ "$COMPLETION_PROMISE" != "null" ]]; then
|
||||
echo ""
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
echo "CRITICAL - Ralph Loop Completion Promise"
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
echo ""
|
||||
echo "To complete this loop, output this EXACT text:"
|
||||
echo " <promise>$COMPLETION_PROMISE</promise>"
|
||||
echo ""
|
||||
echo "STRICT REQUIREMENTS (DO NOT VIOLATE):"
|
||||
echo " ✓ Use <promise> XML tags EXACTLY as shown above"
|
||||
echo " ✓ The statement MUST be completely and unequivocally TRUE"
|
||||
echo " ✓ Do NOT output false statements to exit the loop"
|
||||
echo " ✓ Do NOT lie even if you think you should exit"
|
||||
echo ""
|
||||
echo "IMPORTANT - Do not circumvent the loop:"
|
||||
echo " Even if you believe you're stuck, the task is impossible,"
|
||||
echo " or you've been running too long - you MUST NOT output a"
|
||||
echo " false promise statement. The loop is designed to continue"
|
||||
echo " until the promise is GENUINELY TRUE. Trust the process."
|
||||
echo ""
|
||||
echo " If the loop should stop, the promise statement will become"
|
||||
echo " true naturally. Do not force it by lying."
|
||||
echo "═══════════════════════════════════════════════════════════"
|
||||
fi
|
||||
|
||||
100
scripts/comment-on-duplicates.sh
Executable file
100
scripts/comment-on-duplicates.sh
Executable file
@@ -0,0 +1,100 @@
|
||||
#!/usr/bin/env bash
|
||||
#
|
||||
# Comments on a GitHub issue with a list of potential duplicates.
|
||||
# Usage: ./comment-on-duplicates.sh --base-issue 123 --potential-duplicates 456 789 101
|
||||
#
|
||||
|
||||
set -euo pipefail
|
||||
|
||||
REPO="anthropics/claude-code"
|
||||
BASE_ISSUE=""
|
||||
DUPLICATES=()
|
||||
|
||||
# Parse arguments
|
||||
while [[ $# -gt 0 ]]; do
|
||||
case $1 in
|
||||
--base-issue)
|
||||
BASE_ISSUE="$2"
|
||||
shift 2
|
||||
;;
|
||||
--potential-duplicates)
|
||||
shift
|
||||
while [[ $# -gt 0 && ! "$1" =~ ^-- ]]; do
|
||||
DUPLICATES+=("$1")
|
||||
shift
|
||||
done
|
||||
;;
|
||||
*)
|
||||
echo "Unknown option: $1" >&2
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
# Validate base issue
|
||||
if [[ -z "$BASE_ISSUE" ]]; then
|
||||
echo "Error: --base-issue is required" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if ! [[ "$BASE_ISSUE" =~ ^[0-9]+$ ]]; then
|
||||
echo "Error: --base-issue must be a number, got: $BASE_ISSUE" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Validate duplicates
|
||||
if [[ ${#DUPLICATES[@]} -eq 0 ]]; then
|
||||
echo "Error: --potential-duplicates requires at least one issue number" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if [[ ${#DUPLICATES[@]} -gt 3 ]]; then
|
||||
echo "Error: --potential-duplicates accepts at most 3 issues" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
for dup in "${DUPLICATES[@]}"; do
|
||||
if ! [[ "$dup" =~ ^[0-9]+$ ]]; then
|
||||
echo "Error: duplicate issue must be a number, got: $dup" >&2
|
||||
exit 1
|
||||
fi
|
||||
done
|
||||
|
||||
# Validate that base issue exists
|
||||
if ! gh issue view "$BASE_ISSUE" --repo "$REPO" &>/dev/null; then
|
||||
echo "Error: issue #$BASE_ISSUE does not exist in $REPO" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Validate that all duplicate issues exist
|
||||
for dup in "${DUPLICATES[@]}"; do
|
||||
if ! gh issue view "$dup" --repo "$REPO" &>/dev/null; then
|
||||
echo "Error: issue #$dup does not exist in $REPO" >&2
|
||||
exit 1
|
||||
fi
|
||||
done
|
||||
|
||||
# Build comment body
|
||||
COUNT=${#DUPLICATES[@]}
|
||||
if [[ $COUNT -eq 1 ]]; then
|
||||
HEADER="Found 1 possible duplicate issue:"
|
||||
else
|
||||
HEADER="Found $COUNT possible duplicate issues:"
|
||||
fi
|
||||
|
||||
BODY="$HEADER"$'\n\n'
|
||||
INDEX=1
|
||||
for dup in "${DUPLICATES[@]}"; do
|
||||
BODY+="$INDEX. https://github.com/$REPO/issues/$dup"$'\n'
|
||||
((INDEX++))
|
||||
done
|
||||
|
||||
BODY+=$'\n'"This issue will be automatically closed as a duplicate in 3 days."$'\n\n'
|
||||
BODY+="- If your issue is a duplicate, please close it and 👍 the existing issue instead"$'\n'
|
||||
BODY+="- To prevent auto-closure, add a comment or 👎 this comment"$'\n\n'
|
||||
BODY+="🤖 Generated with [Claude Code](https://claude.ai/code)"
|
||||
|
||||
# Post the comment
|
||||
gh issue comment "$BASE_ISSUE" --repo "$REPO" --body "$BODY"
|
||||
|
||||
echo "Posted duplicate comment on issue #$BASE_ISSUE"
|
||||
Reference in New Issue
Block a user