[BUG] /export command missing from slash command list in specific project folder

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment

Claude Code version: 2.1.205 (commit 4cf2699a1427)
Install method: npm-global
Platform: win32-x64 (Windows)
Path: C:\Users\xxxxx\AppData\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe
claude doctor output: no installation issues found, auto-updates enabled, on latest channel

Bug description
/export does not appear in the slash command list when working inside one specific project folder (D:\projects\handoff-tool), even though it works normally in other project folders and outside any project directory.

Typing / and browsing the full unfiltered list shows commands like /effort and /extra-usage, but no /export anywhere in the list
Typing /export in full does not autocomplete or match anything
This is folder-specific: cd-ing to a different project or running claude outside a project directory shows /export normally
Typing / and browsing the full unfiltered list shows /effort and /extra-usage for the "e"-prefixed commands, but no /export

What I've ruled out

Global ~/.claude/settings.json — contains only unrelated permission allow rules, no deny rules
Project-level .claude/settings.local.json — same, only unrelated permission allow rules
No .claude/commands/ folder in the project (so no custom command is shadowing the built-in)
No .mcp.json in the project
No .env file, no .vscode/settings.json, no unusual CLAUDE.md
claude doctor reports no installation issues
/export does not appear even when typed in full, instead /insights shows up in the Slash Commands list

One anomaly found
In ~/.claude.json, there are two separate project entries for the same physical folder, differing only in path casing:
"d:/Projects/handoff-tool": { "hasTrustDialogAccepted": false, ... }
"D:/projects/handoff-tool": { "hasTrustDialogAccepted": true, ... }
Both have empty mcpServers, allowedTools, etc. Not confirmed as the cause, but seemed worth flagging since Windows paths are case-insensitive but this config appears to key them case-sensitively.
Expected behavior
/export should appear in the slash command list in every project folder, consistent with its presence outside project folders and in other projects.

What Should Happen?

/export should start the /export process not the /insights process

Error Messages/Logs

Claude Code Doctor — Report
Good news: your setup is clean. There's nothing installed that's unused, no leftover config, no CLAUDE.md bloat, and your permission settings are already close to ideal. Only a small number of things were even present to check, since you have no custom skills, plugins, or MCP servers (connections to external tools) installed — just the bundled ones that ship with Claude Code.

Scan window: 5 transcript files, all from this one project (d:\Projects\handoff-tool), spanning 2026-07-08 to 2026-07-09 (4 sessions).

Component	Type	Scope	Uses (total since install)	Used in window?	Est. resident tokens	Verdict
run, insights, doctor	skills (bundled)	user	2 / 4 / 2	yes	~15 each (listing entry)	not touching (bundled)
other built-in skills (dataviz, artifact-design, verify, code-review, etc.)	skills (bundled)	user	n/a	no signal in window	~15 each	not touching (bundled)
—	plugins	—	none installed	—	—	n/a
—	MCP servers	—	none configured	—	—	n/a
—	CLAUDE.md (any location)	—	none found	—	—	n/a
Check-by-check
Check 0 (setup health): Single install, npm-global, matches installMethod. No native-launcher/npm-local duplication, no PATH issues. All settings files (~/.claude/settings.json, .claude/settings.local.json, ~/.claude.json) parse cleanly. No .claude/agents/ files anywhere (project or user) — nothing to validate or deduplicate.
Check 1 (unused extensions): No user-installed skills, plugins, or MCP servers exist to prune. The three claude.ai connectors (Gmail, Calendar, Drive) shown as needing authorization are separate from local config — nothing here can enable/disable them; that's done via claude.ai connector settings if you want them.
Check 2 (LOCAL CLAUDE.md dedup): No CLAUDE.md or CLAUDE.local.md files exist at any level (project, .claude/, or ~/.claude/) — nothing to dedupe.
Check 3 (lazy-loading migration): Same reason — no CLAUDE.md content to migrate.
Check 4 (slow hooks): No hooks configured in any settings file, and zero hook-run entries in transcripts — nothing to warn about.
Check 5 (context-heavy extensions): With no CLAUDE.md, no custom skills, and no MCP servers, the only resident cost is the built-in skill listing (small, and not something you can trim without disabling bundled functionality).
Check 6 (version): Installed 2.1.205, latest on the latest channel is 2.1.205 — up to date.
Check 7 (auto mode default): Already healthy — permissions.defaultMode is "auto" in ~/.claude/settings.json, and no project/local defaultMode shadows it.
Check 8 (denied read-only commands): Only one denial in the entire scan window, and it was an AskUserQuestion prompt (a design-choice question, not a Bash/MCP command) — out of scope for allowlisting, and there's nothing else to propose.
Since no check surfaced anything actionable, there's nothing to confirm or apply — no cleanup, no permission changes. Your install and config are in good shape as-is.

Steps to Reproduce

type /export and /insights will appear instead!

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.205 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_