Add stale issue management workflows

- Add stale-issue-manager.yml to check and manage inactive issues daily
- Add remove-autoclose-label.yml to remove autoclose label when users comment
- Issues get warning after 30 days of inactivity
- Issues auto-close after 60 days (30 days after warning)
- User comments reset the stale timer by removing autoclose label

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.devcontainer/Dockerfile

@@ -65,8 +65,8 @@ ENV PATH=$PATH:/usr/local/share/npm-global/bin
 ENV SHELL=/bin/zsh
 
 # Set the default editor and visual
-ENV EDITOR=nano
-ENV VISUAL=nano
+ENV EDITOR nano
+ENV VISUAL nano
 
 # Default powerline10k theme
 ARG ZSH_IN_DOCKER_VERSION=1.2.0

.devcontainer/devcontainer.json

@@ -16,7 +16,6 @@
   "customizations": {
     "vscode": {
       "extensions": [
-        "anthropic.claude-code",
         "dbaeumer.vscode-eslint",
         "esbenp.prettier-vscode",
         "eamodio.gitlens"
@@ -52,6 +51,5 @@
   },
   "workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind,consistency=delegated",
   "workspaceFolder": "/workspace",
-  "postStartCommand": "sudo /usr/local/bin/init-firewall.sh",
-  "waitFor": "postStartCommand"
+  "postCreateCommand": "sudo /usr/local/bin/init-firewall.sh"
 }

.devcontainer/init-firewall.sh

@@ -69,10 +69,7 @@ for domain in \
     "api.anthropic.com" \
     "sentry.io" \
     "statsig.anthropic.com" \
-    "statsig.com" \
-    "marketplace.visualstudio.com" \
-    "vscode.blob.core.windows.net" \
-    "update.code.visualstudio.com"; do
+    "statsig.com"; do
     echo "Resolving $domain..."
     ips=$(dig +noall +answer A "$domain" | awk '$4 == "A" {print $5}')
     if [ -z "$ips" ]; then
@@ -116,9 +113,6 @@ iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
 # Then allow only specific outbound traffic to allowed domains
 iptables -A OUTPUT -m set --match-set allowed-domains dst -j ACCEPT
 
-# Explicitly REJECT all other outbound traffic for immediate feedback
-iptables -A OUTPUT -j REJECT --reject-with icmp-admin-prohibited
-
 echo "Firewall configuration complete"
 echo "Verifying firewall rules..."
 if curl --connect-timeout 5 https://example.com >/dev/null 2>&1; then

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Environment
+- Platform (select one):
+  - [ ] Anthropic API
+  - [ ] AWS Bedrock
+  - [ ] Google Vertex AI
+  - [ ] Other: <!-- specify -->
+- Claude CLI version: <!-- output of `claude --version` -->
+- Operating System: <!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 -->
+- Terminal:  <!-- e.g. iTerm2, Terminal App -->
+
+## Bug Description
+<!-- A clear and concise description of the bug -->
+
+## Steps to Reproduce
+1. <!-- First step -->
+2. <!-- Second step -->
+3. <!-- And so on... -->
+
+## Expected Behavior
+<!-- What you expected to happen -->
+
+## Actual Behavior
+<!-- What actually happened -->
+
+## Additional Context
+<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,188 +0,0 @@
-name: 🐛 Bug Report
-description: Report a bug or unexpected behavior in Claude Code
-title: "[BUG] "
-labels:
-  - bug
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to report this bug! Please fill out the sections below to help us understand and fix the issue.
-        
-        Before submitting, please check:
-        - You're using the [latest version](https://www.npmjs.com/package/@anthropic-ai/claude-code?activeTab=versions) of Claude Code (`claude --version`) 
-        - This issue hasn't already been reported by searching [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug).
-        - This is a bug, not a feature request or support question
-        
-  - type: checkboxes
-    id: preflight
-    attributes:
-      label: Preflight Checklist
-      description: Please confirm before submitting
-      options:
-        - label: I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
-          required: true
-        - label: This is a single bug report (please file separate reports for different bugs)
-          required: true
-        - label: I am using the latest version of Claude Code
-          required: true
-          
-  - type: textarea
-    id: actual
-    attributes:
-      label: What's Wrong?
-      description: Describe what's happening that shouldn't be
-      placeholder: |
-        When I try to create a Python file, Claude shows an error "EACCES: permission denied" and the file isn't created.
-        
-        The command fails immediately after accepting the file write permission...
-    validations:
-      required: true
-      
-  - type: textarea
-    id: expected
-    attributes:
-      label: What Should Happen?
-      description: Describe the expected behavior
-      placeholder: Claude should create a Python script file successfully without errors
-    validations:
-      required: true
-      
-  - type: textarea
-    id: error_output
-    attributes:
-      label: Error Messages/Logs
-      description: If you see any error messages, paste them here
-      placeholder: |
-        Paste any error output, stack traces, or relevant logs here.
-        This will be automatically formatted as code.
-      render: shell
-    validations:
-      required: false
-      
-  - type: textarea
-    id: reproduction
-    attributes:
-      label: Steps to Reproduce
-      description: |
-        Please provide clear, numbered steps that anyone can follow to reproduce the issue.
-        **Important**: Include any necessary code, file contents, or context needed to reproduce the bug.
-        If the issue involves specific files or code, please create a minimal example.
-      placeholder: |
-        1. Create a file `test.py` with this content:
-           ```python
-           def hello():
-               print("test")
-           ```
-        2. Run `claude "add type hints to test.py"`
-        3. When prompted for file access, accept
-        4. Error appears: "Unable to parse..."
-        
-        Note: The bug only happens with Python files containing...
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: model
-    attributes:
-      label: Claude Model
-      description: Which model were you using? (Run `/model` to check)
-      options:
-        - Sonnet (default)
-        - Opus
-        - Not sure / Multiple models
-        - Other
-    validations:
-      required: false
-      
-  - type: dropdown
-    id: regression
-    attributes:
-      label: Is this a regression?
-      description: Did this work in a previous version? 
-      options:
-        - "Yes, this worked in a previous version"
-        - "No, this never worked"
-        - "I don't know"
-    validations:
-      required: true
-      
-  - type: input
-    id: working_version
-    attributes:
-      label: Last Working Version
-      description: If this is a regression, which version last worked? This helps expedite a fix.
-      placeholder: "e.g., 1.0.100"
-    validations:
-      required: false
-      
-  - type: input
-    id: version
-    attributes:
-      label: Claude Code Version
-      description: Run `claude --version` and paste the output
-      placeholder: "e.g., 1.0.123 (Claude Code)"
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: platform
-    attributes:
-      label: Platform
-      description: Which API platform are you using?
-      options:
-        - Anthropic API
-        - AWS Bedrock
-        - Google Vertex AI
-        - Other
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: os
-    attributes:
-      label: Operating System
-      options:
-        - macOS
-        - Windows
-        - Ubuntu/Debian Linux
-        - Other Linux
-        - Other
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: terminal
-    attributes:
-      label: Terminal/Shell
-      description: Which terminal are you using?
-      options:
-        - Terminal.app (macOS)
-        - Warp
-        - Cursor
-        - iTerm2
-        - IntelliJ IDEA terminal
-        - VS Code integrated terminal
-        - PyCharm terminal
-        - Windows Terminal        
-        - PowerShell
-        - WSL (Windows Subsystem for Linux)
-        - Xterm
-        - Non-interactive/CI environment
-        - Other
-    validations:
-      required: true
-      
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Information
-      description: |
-        Anything else that might help us understand the issue?
-        - Screenshots (drag and drop images here)
-        - Configuration files
-        - Related files or code
-        - Links to repositories demonstrating the issue
-      placeholder: Any additional context, screenshots, or information...
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 💬 Discord Community
-    url: https://anthropic.com/discord
-    about: Get help, ask questions, and chat with other Claude Code users
-  - name: 📖 Documentation
-    url: https://docs.claude.com/en/docs/claude-code
-    about: Read the official documentation and guides
-  - name: 🎓 Getting Started Guide
-    url: https://docs.claude.com/en/docs/claude-code/quickstart
-    about: New to Claude Code? Start here
-  - name: 🔧 Troubleshooting Guide
-    url: https://docs.claude.com/en/docs/claude-code/troubleshooting
-    about: Common issues and how to fix them

.github/ISSUE_TEMPLATE/documentation.yml

@@ -1,117 +0,0 @@
-name: 📚 Documentation Issue
-description: Report missing, unclear, or incorrect documentation
-title: "[DOCS] "
-labels:
-  - documentation
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Help us improve our documentation!
-        
-        Good documentation is crucial for a great developer experience. Please let us know what's missing or confusing.
-        
-  - type: dropdown
-    id: doc_type
-    attributes:
-      label: Documentation Type
-      description: What kind of documentation issue is this?
-      options:
-        - Missing documentation (feature not documented)
-        - Unclear/confusing documentation
-        - Incorrect/outdated documentation
-        - Typo or formatting issue
-        - Missing code examples
-        - Broken links
-        - Other
-    validations:
-      required: true
-      
-  - type: input
-    id: location
-    attributes:
-      label: Documentation Location
-      description: Where did you encounter this issue? Provide a URL if possible
-      placeholder: "e.g., https://docs.anthropic.com/en/docs/claude-code/getting-started"
-    validations:
-      required: false
-      
-  - type: input
-    id: section
-    attributes:
-      label: Section/Topic
-      description: Which specific section or topic needs improvement?
-      placeholder: "e.g., MCP Server Configuration section"
-    validations:
-      required: true
-      
-  - type: textarea
-    id: current
-    attributes:
-      label: Current Documentation
-      description: |
-        What does the documentation currently say? 
-        Quote the specific text if applicable.
-      placeholder: |
-        The docs currently say:
-        "To configure MCP servers, add them to your configuration..."
-        
-        But it doesn't explain...
-    validations:
-      required: false
-      
-  - type: textarea
-    id: issue
-    attributes:
-      label: What's Wrong or Missing?
-      description: Explain what's incorrect, unclear, or missing
-      placeholder: |
-        The documentation doesn't explain how to:
-        - Configure multiple MCP servers
-        - Handle authentication
-        - Debug connection issues
-        
-        The example code doesn't work because...
-    validations:
-      required: true
-      
-  - type: textarea
-    id: suggested
-    attributes:
-      label: Suggested Improvement
-      description: How should the documentation be improved? Provide suggested text if possible
-      placeholder: |
-        The documentation should include:
-        
-        1. A complete example showing...
-        2. Explanation of common errors like...
-        3. Step-by-step guide for...
-        
-        Suggested text:
-        "To configure multiple MCP servers, create an array in your settings..."
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: impact
-    attributes:
-      label: Impact
-      description: How much does this documentation issue affect users?
-      options:
-        - High - Prevents users from using a feature
-        - Medium - Makes feature difficult to understand
-        - Low - Minor confusion or inconvenience
-    validations:
-      required: true
-          
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: |
-        - Screenshots showing the issue
-        - Links to related documentation
-        - Examples from other projects that do this well
-      placeholder: Any additional information that would help...
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,132 +0,0 @@
-name: ✨ Feature Request
-description: Suggest a new feature or enhancement for Claude Code
-title: "[FEATURE] "
-labels:
-  - enhancement
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Thanks for suggesting a feature!
-        
-        We love hearing ideas from our community. Please help us understand your use case by filling out the sections below.
-        Before submitting, please check if this feature has already been requested.
-        
-  - type: checkboxes
-    id: preflight
-    attributes:
-      label: Preflight Checklist
-      options:
-        - label: I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet
-          required: true
-        - label: This is a single feature request (not multiple features)
-          required: true
-          
-  - type: textarea
-    id: problem
-    attributes:
-      label: Problem Statement
-      description: |
-        What problem are you trying to solve? Why do you need this feature?
-        Focus on the problem, not the solution. Help us understand your workflow.
-      placeholder: |
-        I often need to work with multiple projects simultaneously, but Claude Code doesn't support...
-        
-        When I'm debugging code, I find it difficult to...
-        
-        The current workflow requires me to manually...
-    validations:
-      required: true
-      
-  - type: textarea
-    id: solution
-    attributes:
-      label: Proposed Solution
-      description: |
-        How would you like this to work? Describe the ideal user experience.
-        Be specific about how you'd interact with this feature.
-      placeholder: |
-        I'd like to be able to run `claude --workspace project1,project2` to...
-        
-        There should be a command or setting that allows...
-        
-        The interface should show...
-    validations:
-      required: true
-      
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternative Solutions
-      description: |
-        What alternatives have you considered or tried?
-        Are there workarounds you're currently using?
-      placeholder: |
-        I've tried using multiple terminal windows but...
-        
-        Currently I work around this by...
-        
-        Other tools solve this by...
-    validations:
-      required: false
-      
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: How important is this feature to your workflow?
-      options:
-        - Critical - Blocking my work
-        - High - Significant impact on productivity
-        - Medium - Would be very helpful
-        - Low - Nice to have
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: category
-    attributes:
-      label: Feature Category
-      description: What area does this feature relate to?
-      options:
-        - CLI commands and flags
-        - Interactive mode (TUI)
-        - File operations
-        - API and model interactions
-        - MCP server integration
-        - Performance and speed
-        - Configuration and settings
-        - Developer tools/SDK
-        - Documentation
-        - Other
-    validations:
-      required: true
-      
-  - type: textarea
-    id: use_case
-    attributes:
-      label: Use Case Example
-      description: |
-        Provide a concrete, real-world example of when you'd use this feature.
-        Walk us through a scenario step-by-step.
-      placeholder: |
-        Example scenario:
-        1. I'm working on a React app with a Node.js backend
-        2. I need to make changes to both frontend and backend
-        3. With this feature, I could...
-        4. This would save me time because...
-    validations:
-      required: false
-      
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: |
-        - Screenshots or mockups of the proposed feature
-        - Links to similar features in other tools
-        - Technical considerations or constraints
-        - Any other relevant information
-      placeholder: Add any other context, mockups, or examples here...
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/model_behavior.yml

@@ -1,220 +0,0 @@
-name: 🤖 Model Behavior Issue
-description: Report unexpected Claude model behavior, incorrect actions, or permission violations
-title: "[MODEL] "
-labels:
-  - model
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Report Unexpected Model Behavior
-        
-        Use this template when Claude does something unexpected, makes unwanted changes, or behaves inconsistently with your instructions.
-        
-        **This is for:** Unexpected actions, file modifications outside scope, ignoring instructions, making assumptions
-        **NOT for:** Crashes, API errors, or installation issues (use Bug Report instead)
-        
-  - type: checkboxes
-    id: preflight
-    attributes:
-      label: Preflight Checklist
-      description: Please confirm before submitting
-      options:
-        - label: I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Amodel) for similar behavior reports
-          required: true
-        - label: This report does NOT contain sensitive information (API keys, passwords, etc.)
-          required: true
-          
-  - type: dropdown
-    id: behavior_type
-    attributes:
-      label: Type of Behavior Issue
-      description: What category best describes the unexpected behavior?
-      options:
-        - Claude modified files I didn't ask it to modify
-        - Claude accessed files outside the working directory
-        - Claude ignored my instructions or configuration
-        - Claude reverted/undid previous changes without asking
-        - Claude made incorrect assumptions about my project
-        - Claude refused a reasonable request
-        - Claude's behavior changed between sessions
-        - Subagent behaved unexpectedly
-        - Other unexpected behavior
-    validations:
-      required: true
-      
-  - type: textarea
-    id: what_you_asked
-    attributes:
-      label: What You Asked Claude to Do
-      description: Provide the exact prompt or command you gave
-      placeholder: |
-        I asked: "Update the README.md file to add installation instructions"
-        
-        Or I ran: `claude "fix the bug in auth.js"`
-    validations:
-      required: true
-      
-  - type: textarea
-    id: what_claude_did
-    attributes:
-      label: What Claude Actually Did
-      description: Describe step-by-step what Claude did instead
-      placeholder: |
-        1. Claude read README.md
-        2. Instead of updating it, Claude deleted the entire file
-        3. Created a new README from scratch with different content
-        4. Also modified package.json without being asked
-        5. Changed .gitignore file
-    validations:
-      required: true
-      
-  - type: textarea
-    id: expected_behavior
-    attributes:
-      label: Expected Behavior
-      description: What should Claude have done?
-      placeholder: |
-        Claude should have:
-        1. Read the existing README.md
-        2. Added an "Installation" section
-        3. Only modified that single file
-        4. Not touched any other files
-    validations:
-      required: true
-      
-  - type: textarea
-    id: files_affected
-    attributes:
-      label: Files Affected
-      description: |
-        List all files that were accessed or modified (even if you didn't expect them to be)
-      placeholder: |
-        Modified:
-        - README.md (deleted and recreated)
-        - package.json (version bumped - not requested)
-        - .gitignore (added entries - not requested)
-        
-        Read (unexpectedly):
-        - /Users/me/.ssh/config
-        - ../../../parent-directory/secrets.env
-      render: shell
-    validations:
-      required: false
-      
-  - type: dropdown
-    id: permission_mode
-    attributes:
-      label: Permission Mode
-      description: What permission settings were active?
-      options:
-        - Accept Edits was ON (auto-accepting changes)
-        - Accept Edits was OFF (manual approval required)
-        - I don't know / Not sure
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: reproducible
-    attributes:
-      label: Can You Reproduce This?
-      description: Does this happen consistently?
-      options:
-        - Yes, every time with the same prompt
-        - Sometimes (intermittent)
-        - No, only happened once
-        - Haven't tried to reproduce
-    validations:
-      required: true
-      
-  - type: textarea
-    id: reproduction_steps
-    attributes:
-      label: Steps to Reproduce
-      description: If reproducible, provide minimal steps
-      placeholder: |
-        1. Create a new directory with a simple README.md
-        2. Ask Claude Code to "improve the README"
-        3. Claude will delete and recreate the file instead of editing
-    validations:
-      required: false
-      
-  - type: dropdown
-    id: model
-    attributes:
-      label: Claude Model
-      description: Which model were you using? (Run `/model` to check)
-      options:
-        - Sonnet
-        - Opus
-        - Haiku
-        - Not sure
-        - Other
-    validations:
-      required: true
-      
-  - type: textarea
-    id: conversation_log
-    attributes:
-      label: Relevant Conversation
-      description: |
-        Include relevant parts of Claude's responses, especially where it explains what it's doing
-      placeholder: |
-        Claude said: "I'll help you update the README. Let me first delete the old one and create a fresh version..."
-        
-        [Then proceeded to delete without asking for confirmation]
-      render: markdown
-    validations:
-      required: false
-      
-  - type: dropdown
-    id: impact
-    attributes:
-      label: Impact
-      description: How severe was the impact of this behavior?
-      options:
-        - Critical - Data loss or corrupted project
-        - High - Significant unwanted changes
-        - Medium - Extra work to undo changes
-        - Low - Minor inconvenience
-    validations:
-      required: true
-      
-  - type: input
-    id: version
-    attributes:
-      label: Claude Code Version
-      description: Run `claude --version` and paste the output
-      placeholder: "e.g., 1.0.123 (Claude Code)"
-    validations:
-      required: true
-      
-  - type: dropdown
-    id: platform
-    attributes:
-      label: Platform
-      description: Which API platform are you using?
-      options:
-        - Anthropic API
-        - AWS Bedrock
-        - Google Vertex AI
-        - Other
-    validations:
-      required: true
-      
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: |
-        - Any patterns you've noticed
-        - Similar behavior in other sessions
-        - Specific file types or project structures that trigger this
-        - Screenshots if relevant
-      placeholder: |
-        This seems to happen more often with:
-        - Python projects
-        - When there are multiple similar files
-        - After long conversations
-    validations:
-      required: false

.github/workflows/issue-opened-dispatch.yml

@@ -1,28 +0,0 @@
-name: Issue Opened Dispatch
-
-on:
-  issues:
-    types: [opened]
-
-permissions:
-  issues: read
-  actions: write
-
-jobs:
-  notify:
-    runs-on: ubuntu-latest
-    timeout-minutes: 1
-    steps:
-      - name: Process new issue
-        env:
-          ISSUE_URL: ${{ github.event.issue.html_url }}
-          ISSUE_NUMBER: ${{ github.event.issue.number }}
-          ISSUE_TITLE: ${{ github.event.issue.title }}
-          TARGET_REPO: ${{ secrets.ISSUE_OPENED_DISPATCH_TARGET_REPO }}
-          GH_TOKEN: ${{ secrets.ISSUE_OPENED_DISPATCH_TOKEN }}
-        run: |
-          gh api repos/${TARGET_REPO}/dispatches \
-            -f event_type=issue_opened \
-            -f client_payload[issue_url]="${ISSUE_URL}" || {
-              exit 0
-            }

.github/workflows/log-issue-events.yml

@@ -2,7 +2,7 @@ name: Log Issue Events to Statsig
 
 on:
   issues:
-    types: [opened, closed]
+    types: [opened]
 
 jobs:
   log-to-statsig:

.github/workflows/remove-autoclose-label.yml

@@ -0,0 +1,42 @@
+name: "Remove Autoclose Label on Activity"
+
+on:
+  issue_comment:
+    types: [created]
+
+permissions:
+  issues: write
+
+jobs:
+  remove-autoclose:
+    # Only run if the issue has the autoclose label
+    if: |
+      github.event.issue.state == 'open' &&
+      contains(github.event.issue.labels.*.name, 'autoclose') &&
+      github.event.comment.user.login != 'github-actions[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Remove autoclose label
+        uses: actions/github-script@v7
+        with:
+          script: |
+            console.log(`Removing autoclose label from issue #${context.issue.number} due to new comment from ${context.payload.comment.user.login}`);
+            
+            try {
+              // Remove the autoclose label
+              await github.rest.issues.removeLabel({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.issue.number,
+                name: 'autoclose'
+              });
+              
+              console.log(`Successfully removed autoclose label from issue #${context.issue.number}`);
+            } catch (error) {
+              // If the label was already removed or doesn't exist, that's fine
+              if (error.status === 404) {
+                console.log(`Autoclose label was already removed from issue #${context.issue.number}`);
+              } else {
+                throw error;
+              }
+            }

.github/workflows/stale-issue-manager.yml

@@ -0,0 +1,157 @@
+name: "Manage Stale Issues"
+
+on:
+  schedule:
+    # 2am Pacific = 9am UTC (10am UTC during DST)
+    - cron: "0 10 * * *"
+  workflow_dispatch:
+
+permissions:
+  issues: write
+
+concurrency:
+  group: stale-issue-manager
+
+jobs:
+  manage-stale-issues:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Manage stale issues
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const oneMonthAgo = new Date();
+            oneMonthAgo.setDate(oneMonthAgo.getDate() - 30);
+
+            const twoMonthsAgo = new Date();
+            twoMonthsAgo.setDate(twoMonthsAgo.getDate() - 60);
+
+            const warningComment = `This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.`;
+
+            const closingComment = `This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.`;
+
+            let page = 1;
+            let hasMore = true;
+            let totalWarned = 0;
+            let totalClosed = 0;
+            let totalLabeled = 0;
+
+            while (hasMore) {
+              // Get open issues sorted by last updated (oldest first)
+              const { data: issues } = await github.rest.issues.listForRepo({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                state: 'open',
+                sort: 'updated',
+                direction: 'asc',
+                per_page: 100,
+                page: page
+              });
+              
+              if (issues.length === 0) {
+                hasMore = false;
+                break;
+              }
+              
+              for (const issue of issues) {
+                // Skip if already locked
+                if (issue.locked) continue;
+                
+                // Skip pull requests
+                if (issue.pull_request) continue;
+                
+                // Check if updated more recently than 30 days ago
+                const updatedAt = new Date(issue.updated_at);
+                if (updatedAt > oneMonthAgo) {
+                  // Since issues are sorted by updated_at ascending, 
+                  // once we hit a recent issue, all remaining will be recent too
+                  hasMore = false;
+                  break;
+                }
+                
+                // Check if issue has autoclose label
+                const hasAutocloseLabel = issue.labels.some(label => 
+                  typeof label === 'object' && label.name === 'autoclose'
+                );
+                
+                try {
+                  // Get comments to check for existing warning
+                  const { data: comments } = await github.rest.issues.listComments({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issue.number,
+                    per_page: 100
+                  });
+                  
+                  // Find the last comment from github-actions bot
+                  const botComments = comments.filter(comment => 
+                    comment.user && comment.user.login === 'github-actions[bot]' &&
+                    comment.body && comment.body.includes('inactive for 30 days')
+                  );
+                  
+                  const lastBotComment = botComments[botComments.length - 1];
+                  
+                  if (lastBotComment) {
+                    // Check if the bot comment is older than 30 days (total 60 days of inactivity)
+                    const botCommentDate = new Date(lastBotComment.created_at);
+                    if (botCommentDate < oneMonthAgo) {
+                      // Close the issue - it's been stale for 60+ days
+                      console.log(`Closing issue #${issue.number} (stale for 60+ days): ${issue.title}`);
+                      
+                      // Post closing comment
+                      await github.rest.issues.createComment({
+                        owner: context.repo.owner,
+                        repo: context.repo.repo,
+                        issue_number: issue.number,
+                        body: closingComment
+                      });
+                      
+                      // Close the issue
+                      await github.rest.issues.update({
+                        owner: context.repo.owner,
+                        repo: context.repo.repo,
+                        issue_number: issue.number,
+                        state: 'closed',
+                        state_reason: 'not_planned'
+                      });
+                      
+                      totalClosed++;
+                    }
+                    // If bot comment exists but is recent, issue already has warning
+                  } else if (updatedAt < oneMonthAgo) {
+                    // No bot warning yet, issue is 30+ days old
+                    console.log(`Warning issue #${issue.number} (stale for 30+ days): ${issue.title}`);
+                    
+                    // Post warning comment
+                    await github.rest.issues.createComment({
+                      owner: context.repo.owner,
+                      repo: context.repo.repo,
+                      issue_number: issue.number,
+                      body: warningComment
+                    });
+                    
+                    totalWarned++;
+                    
+                    // Add autoclose label if not present
+                    if (!hasAutocloseLabel) {
+                      await github.rest.issues.addLabels({
+                        owner: context.repo.owner,
+                        repo: context.repo.repo,
+                        issue_number: issue.number,
+                        labels: ['autoclose']
+                      });
+                      totalLabeled++;
+                    }
+                  }
+                } catch (error) {
+                  console.error(`Failed to process issue #${issue.number}: ${error.message}`);
+                }
+              }
+              
+              page++;
+            }
+
+            console.log(`Summary:`);
+            console.log(`- Issues warned (30 days stale): ${totalWarned}`);
+            console.log(`- Issues labeled with autoclose: ${totalLabeled}`);
+            console.log(`- Issues closed (60 days stale): ${totalClosed}`);

CHANGELOG.md

@@ -1,112 +1,5 @@
 # Changelog
 
-## 1.0.126
-
-- Enable /context command for Bedrock and Vertex
-- Add mTLS support for HTTP-based OpenTelemetry exporters
-
-## 1.0.124
-
-- Set `CLAUDE_BASH_NO_LOGIN` environment variable to 1 or true to to skip login shell for BashTool
-- Fix Bedrock and Vertex environment variables evaluating all strings as truthy
-- No longer inform Claude of the list of allowed tools when permission is denied
-- Fixed security vulnerability in Bash tool permission checks
-- Improved VSCode extension performance for large files
-
-## 1.0.123
-
-- Bash permission rules now support output redirections when matching (e.g., `Bash(python:*)` matches `python script.py > output.txt`)
-- Fixed thinking mode triggering on negation phrases like "don't think"
-- Fixed rendering performance degradation during token streaming
-- Added SlashCommand tool, which enables Claude to invoke your slash commands. https://docs.claude.com/en/docs/claude-code/slash-commands#SlashCommand-tool
-- Enhanced BashTool environment snapshot logging
-- Fixed a bug where resuming a conversation in headless mode would sometimes enable thinking unnecessarily
-- Migrated --debug logging to a file, to enable easy tailing & filtering
-
-## 1.0.120
-
-- Fix input lag during typing, especially noticeable with large prompts
-- Improved VSCode extension command registry and sessions dialog user experience
-- Enhanced sessions dialog responsiveness and visual feedback
-- Fixed IDE compatibility issue by removing worktree support check
-- Fixed security vulnerability where Bash tool permission checks could be bypassed using prefix matching
-
-## 1.0.119
-
-- Fix Windows issue where process visually freezes on entering interactive mode
-- Support dynamic headers for MCP servers via headersHelper configuration
-- Fix thinking mode not working in headless sessions
-- Fix slash commands now properly update allowed tools instead of replacing them
-
-## 1.0.117
-
-- Add Ctrl-R history search to recall previous commands like bash/zsh
-- Fix input lag while typing, especially on Windows
-- Add sed command to auto-allowed commands in acceptEdits mode
-- Fix Windows PATH comparison to be case-insensitive for drive letters
-- Add permissions management hint to /add-dir output
-
-## 1.0.115
-
-- Improve thinking mode display with enhanced visual effects
-- Type /t to temporarily disable thinking mode in your prompt
-- Improve path validation for glob and grep tools
-- Show condensed output for post-tool hooks to reduce visual clutter
-- Fix visual feedback when loading state completes
-- Improve UI consistency for permission request dialogs
-
-## 1.0.113
-
-- Deprecated piped input in interactive mode
-- Move Ctrl+R keybinding for toggling transcript to Ctrl+O
-
-## 1.0.112
-
-- Transcript mode (Ctrl+R): Added the model used to generate each assistant message
-- Addressed issue where some Claude Max users were incorrectly recognized as Claude Pro users
-- Hooks: Added systemMessage support for SessionEnd hooks
-- Added `spinnerTipsEnabled` setting to disable spinner tips
-- IDE: Various improvements and bug fixes
-
-## 1.0.111
-
-- /model now validates provided model names
-- Fixed Bash tool crashes caused by malformed shell syntax parsing
-
-## 1.0.110
-
-- /terminal-setup command now supports WezTerm
-- MCP: OAuth tokens now proactively refresh before expiration
-- Fixed reliability issues with background Bash processes
-
-## 1.0.109
-
-- SDK: Added partial message streaming support via `--include-partial-messages` CLI flag
-
-## 1.0.106
-
-- Windows: Fixed path permission matching to consistently use POSIX format (e.g., `Read(//c/Users/...)`)
-
-## 1.0.97
-
-- Settings: /doctor now validates permission rule syntax and suggests corrections
-
-## 1.0.94
-
-- Vertex: add support for global endpoints for supported models
-- /memory command now allows direct editing of all imported memory files
-- SDK: Add custom tools as callbacks
-- Added /todos command to list current todo items
-
-## 1.0.93
-
-- Windows: Add alt + v shortcut for pasting images from clipboard
-- Support NO_PROXY environment variable to bypass proxy for specified hostnames and IPs
-
-## 1.0.90
-
-- Settings file changes take effect immediately - no restart required
-
 ## 1.0.88
 
 - Fixed issue causing "OAuth authentication is currently not supported"
@@ -148,7 +41,7 @@
 
 ## 1.0.81
 
-- Released output styles, including new built-in educational output styles "Explanatory" and "Learning". Docs: https://docs.claude.com/en/docs/claude-code/output-styles
+- Released output styles, including new built-in educational output styles "Explanatory" and "Learning". Docs: https://docs.anthropic.com/en/docs/claude-code/output-styles
 - Agents: Fix custom agent loading when agent files are unparsable
 
 ## 1.0.80
@@ -353,7 +246,7 @@
 
 ## 1.0.38
 
-- Released hooks. Special thanks to community input in https://github.com/anthropics/claude-code/issues/712. Docs: https://docs.claude.com/en/docs/claude-code/hooks
+- Released hooks. Special thanks to community input in https://github.com/anthropics/claude-code/issues/712. Docs: https://docs.anthropic.com/en/docs/claude-code/hooks
 
 ## 1.0.37
 

README.md

@@ -34,7 +34,9 @@ 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).
+We may use feedback to improve our products and services, but we will not train generative models using your feedback from Claude Code. Given their potentially sensitive nature, we store user feedback transcripts for only 30 days.
+
+If you choose to send us feedback about Claude Code, such as transcripts of your usage, Anthropic may use that feedback to debug related issues and improve Claude Code's functionality (e.g., to reduce the risk of similar bugs occurring in the future).
 
 ### Privacy safeguards
 

Script/run_devcontainer_claude_code.ps1

@@ -40,18 +40,14 @@ Write-Host "Using backend: $($Backend)"
 # --- Prerequisite Check ---
 Write-Host "Checking for required commands..."
 try {
-    if (-not (Get-Command $Backend -ErrorAction SilentlyContinue)) {
-        throw "Required command '$($Backend)' not found."
-    }
+    Get-Command $Backend -ErrorAction Stop | Out-Null
     Write-Host "- $($Backend) command found."
-    if (-not (Get-Command devcontainer -ErrorAction SilentlyContinue)) {
-        throw "Required command 'devcontainer' not found."
-    }
+    Get-Command devcontainer -ErrorAction Stop | Out-Null
     Write-Host "- devcontainer command found."
 }
 catch {
-    Write-Error "A required command is not installed or not in your PATH. $($_.Exception.Message)"
-    Write-Error "Please ensure both '$Backend' and 'devcontainer' are installed and accessible in your system's PATH."
+    Write-Error "A required command is not installed or not in your PATH."
+    Write-Error "Please ensure '$($_.Exception.Message.Split(':')[0])' and 'devcontainer' are installed and accessible."
     exit 1
 }
 

scripts/backfill-duplicate-comments.ts

@@ -82,61 +82,46 @@ Usage:
 Environment Variables:
   GITHUB_TOKEN - GitHub personal access token with repo and actions permissions (required)
   DRY_RUN - Set to "false" to actually trigger workflows (default: true for safety)
-  MAX_ISSUE_NUMBER - Only process issues with numbers less than this value (default: 4050)`);
+  DAYS_BACK - How many days back to look for old issues (default: 90)`);
   }
   console.log("[DEBUG] GitHub token found");
 
   const owner = "anthropics";
   const repo = "claude-code";
   const dryRun = process.env.DRY_RUN !== "false";
-  const maxIssueNumber = parseInt(process.env.MAX_ISSUE_NUMBER || "4050", 10);
-  const minIssueNumber = parseInt(process.env.MIN_ISSUE_NUMBER || "1", 10);
+  const daysBack = parseInt(process.env.DAYS_BACK || "90", 10);
   
   console.log(`[DEBUG] Repository: ${owner}/${repo}`);
   console.log(`[DEBUG] Dry run mode: ${dryRun}`);
-  console.log(`[DEBUG] Looking at issues between #${minIssueNumber} and #${maxIssueNumber}`);
+  console.log(`[DEBUG] Looking back ${daysBack} days`);
 
-  console.log(`[DEBUG] Fetching issues between #${minIssueNumber} and #${maxIssueNumber}...`);
+  const cutoffDate = new Date();
+  cutoffDate.setDate(cutoffDate.getDate() - daysBack);
+
+  console.log(`[DEBUG] Fetching issues created since ${cutoffDate.toISOString()}...`);
   const allIssues: GitHubIssue[] = [];
   let page = 1;
   const perPage = 100;
   
   while (true) {
     const pageIssues: GitHubIssue[] = await githubRequest(
-      `/repos/${owner}/${repo}/issues?state=all&per_page=${perPage}&page=${page}&sort=created&direction=desc`,
+      `/repos/${owner}/${repo}/issues?state=all&per_page=${perPage}&page=${page}&since=${cutoffDate.toISOString()}`,
       token
     );
     
     if (pageIssues.length === 0) break;
     
-    // Filter to only include issues within the specified range
-    const filteredIssues = pageIssues.filter(issue => 
-      issue.number >= minIssueNumber && issue.number < maxIssueNumber
-    );
-    allIssues.push(...filteredIssues);
-    
-    // If the oldest issue in this page is still above our minimum, we need to continue
-    // but if the oldest issue is below our minimum, we can stop
-    const oldestIssueInPage = pageIssues[pageIssues.length - 1];
-    if (oldestIssueInPage && oldestIssueInPage.number >= maxIssueNumber) {
-      console.log(`[DEBUG] Oldest issue in page #${page} is #${oldestIssueInPage.number}, continuing...`);
-    } else if (oldestIssueInPage && oldestIssueInPage.number < minIssueNumber) {
-      console.log(`[DEBUG] Oldest issue in page #${page} is #${oldestIssueInPage.number}, below minimum, stopping`);
-      break;
-    } else if (filteredIssues.length === 0 && pageIssues.length > 0) {
-      console.log(`[DEBUG] No issues in page #${page} are in range #${minIssueNumber}-#${maxIssueNumber}, continuing...`);
-    }
-    
+    allIssues.push(...pageIssues);
     page++;
     
     // Safety limit to avoid infinite loops
-    if (page > 200) {
+    if (page > 100) {
       console.log("[DEBUG] Reached page limit, stopping pagination");
       break;
     }
   }
   
-  console.log(`[DEBUG] Found ${allIssues.length} issues between #${minIssueNumber} and #${maxIssueNumber}`);
+  console.log(`[DEBUG] Found ${allIssues.length} issues from the last ${daysBack} days`);
 
   let processedCount = 0;
   let candidateCount = 0;