{"slug": "code-manager", "title": "Code-Manager", "summary": "Code Manager, a new Tauri 2 desktop app, centralizes local configuration and session data for Claude Code users, offering profiles, memory, skills, history, stats, token usage, and diagnostics in a single interface. The tool manages the ~/.claude directory and related files without replacing Claude Code, aiming to simplify configuration review and troubleshooting.", "body_md": "Code Manager is a local desktop management app for Claude Code users. It brings profiles, providers, the `~/.claude`\n\ndirectory, memories, Skills, history, stats, token usage, project status, the system tray, and diagnostic logs together in a single Tauri 2 app, making your local configuration more visible, previewable, and verifiable.\n\nThis document is for human users and project visitors. Execution rules for AI agents are in [CLAUDE.md](/maguowei/code-manager/blob/main/CLAUDE.md), the full usage guide is in [docs/user-manual.md](/maguowei/code-manager/blob/main/docs/user-manual.md), and platform differences are in [docs/platform-support.md](/maguowei/code-manager/blob/main/docs/platform-support.md).\n\nOver long-term use of Claude Code, local configuration and session data tend to scatter across many files:\n\n- Different projects need different models, API endpoints, tokens, permissions, hooks, and plugin combinations.\n`~/.claude/settings.json`\n\n,`CLAUDE.md`\n\n,`rules/*.md`\n\n, and Skills are hard to review as a whole.- Provider / model configuration is repetitive, and switching profiles easily misses environment variables or overrides user settings.\n- History, stats, token spend, project Git status, and worktree information lack a single entry point.\n- Troubleshooting requires quickly viewing redacted application logs instead of hunting for log files everywhere.\n\nCode Manager does not replace Claude Code; it provides a management layer for local configuration, session data, and diagnostic information.\n\n| Capability | Description |\n|---|---|\n`~/.claude` Overview |\nBrowse, preview, edit, and locate the Claude Code user directory. |\n| Profiles / Built-in Providers | Manage the profile layer ultimately written to `~/.claude/settings.json` , picking connection endpoints and model mappings from built-in (read-only) providers. Edit models, environment variables, permissions, Sandbox, hooks, plugins, and the status line. Preview, copy, test models, apply in one click, import an existing settings file, export (optionally with secrets, with a pre-save preview), compare diffs, and sync common options / marketplaces / plugins to other profiles. |\n| Memory Management | Manage user-level `CLAUDE.md` and `rules/*.md` , with support for the Karpathy behavior guide preset, import, enable, disable, copy, preview, and path validation. |\n| Skills Management | Create, edit, delete, enable, and disable Claude Code Skills, and sync them as `~/.codex/skills/<id>` symlinks. |\n| History & Sessions | Read `~/.claude/history.jsonl` and view history details by project and session. |\n| Stats & Recent Sessions | Read a local stats snapshot from `~/.claude.json` . |\n| Token Usage & Cost | Scan `~/.claude/projects/**/*.jsonl` , aggregate tokens and cost by date, project, session, and model, with incremental SQLite caching. |\n| Project Management | Show project paths, remotes, branches, worktrees, project-level `.claude/` , `AGENTS.md` / `CLAUDE.md` , and `.agents/skills` status, with support for opening a terminal/editor, jumping to history/usage, branch and worktree cleanup, and clearing local project data. |\n| System Tray & Session Focus | Show the current profile and active Claude Code sessions in the menu bar, with session-count styles and a pending-session breathing indicator, attempt to focus existing terminal sessions on supported platforms, and (macOS only) mirror session state to ANTICATER USB device LED effects. |\n| Desktop Usage Widget | An always-on-top, translucent mini-window that shows today's token spend, usage, and cache-hit metrics in real time, with drag support, customizable metrics, and adjustable opacity, toggleable in settings. |\n| Settings & Diagnostics | Support language, theme, default-collapsed sidebar, menu-bar session display, system notifications, third-party model pricing, launch at login, default terminal and editor, session-focus shortcut and LED effects (macOS only), desktop usage widget toggle and metric customization, redacted log viewing, system info copy, and log rotation. |\n\nOn macOS, installing via Homebrew (own tap) is recommended:\n\n```\nbrew install --cask maguowei/tap/code-manager\n```\n\nOr go to [Releases](https://github.com/maguowei/code-manager/releases) to download the installer for your platform.\n\n| Platform | Installer |\n|---|---|\n| macOS (Apple Silicon / Intel) | `.dmg` (or `brew install --cask maguowei/tap/code-manager` ) |\n| Windows | `.msi` / `.exe` |\n| Linux | `.deb` / `.rpm` / `.AppImage` |\n\nThe current macOS release packages are not notarized by Apple. Homebrew installs automatically remove the quarantine attribute; if you manually download the `.dmg`\n\nand the first launch is blocked by the system, run the following in a terminal:\n\n```\nxattr -rd com.apple.quarantine /Applications/code-manager.app\n```\n\nThe app has built-in automatic updates: it silently checks for new versions on startup, and once one is found you can download and install it with one click in \"Settings - App Update\", after which it restarts automatically. Users who installed via Homebrew can also keep upgrading with `brew upgrade`\n\n; both paths work, and after an in-app update the version Homebrew records will automatically align on the next `brew upgrade`\n\n.\n\n- After launch, Code Manager reads your local\n`~/.claude`\n\n,`~/.claude.json`\n\n, and`~/.claude/projects/`\n\n. - In settings, choose the interface language, theme, default terminal, and default editor.\n- On the profiles page, import an existing\n`~/.claude/settings.json`\n\n, or create a new profile, pick a built-in provider in the \"Provider\" option, and fill in the auth secret and model configuration. - Click \"Test Model\" to confirm the configuration works.\n- Click enable to apply the profile to\n`~/.claude/settings.json`\n\n. - Go to the\n`~/.claude`\n\noverview to confirm the final configuration is as expected.\n\nFor more detailed page descriptions, cost accounting rules, common workflows, and FAQ, see [docs/user-manual.md](/maguowei/code-manager/blob/main/docs/user-manual.md).\n\nCode Manager mainly reads and writes local files. Profile merging, directory scanning, usage aggregation, and log viewing all happen locally; model pricing prefers the local cache and built-in fallback data, and attempts to refresh from official models.dev providers after startup.\n\n| Purpose | macOS | Linux | Windows |\n|---|---|---|---|\n| Application data | `~/.config/code-manager/` |\n`$XDG_CONFIG_HOME/code-manager/` or `~/.config/code-manager/` |\n`%APPDATA%\\code-manager\\` |\n| Usage SQLite | `~/Library/Application Support/com.gotobeta.app.code-manager/usage.db` |\n`$XDG_CONFIG_HOME/com.gotobeta.app.code-manager/usage.db` or `~/.config/com.gotobeta.app.code-manager/usage.db` |\n`%APPDATA%\\com.gotobeta.app.code-manager\\usage.db` |\n| Log directory | `~/Library/Logs/com.gotobeta.app.code-manager/` |\n`$XDG_DATA_HOME/com.gotobeta.app.code-manager/logs/` or `~/.local/share/com.gotobeta.app.code-manager/logs/` |\n`%LOCALAPPDATA%\\com.gotobeta.app.code-manager\\logs\\` |\n\nThe application data directory contains `config-registry.json`\n\n, `memories.json`\n\n, `model-pricing.json`\n\n, and `skills-disabled/`\n\n. On macOS, application data deliberately uses `~/.config/code-manager/`\n\nfor easier cross-platform backup and script access; SQLite uses Tauri's `app_config_dir()`\n\n, and logs use the Tauri plugin's default path.\n\nStack overview: Tauri 2 + React 19 + TypeScript + Vite + Tailwind CSS v4 + Rust. For full agent execution rules, verification notes, and fine-grained path navigation, see [CLAUDE.md](/maguowei/code-manager/blob/main/CLAUDE.md).\n\n- Node.js LTS\n`pnpm`\n\n, the project currently declares`pnpm@11.2.2`\n\n- Rust stable\n- The system dependencies required to run Tauri 2\n\n```\nmake init             # Install dependencies and check the Rust toolchain\nmake dev              # Start Tauri desktop dev mode\nmake build            # Build the installer for the current platform\nmake build-frontend   # TypeScript check and build the frontend\nmake bindings         # Regenerate Tauri IPC TypeScript bindings\nmake bindings-check   # Check that Rust command contracts and src/bindings.ts are in sync\nmake lint             # Frontend Biome + Rust clippy\nmake test             # Rust tests + frontend tests\nmake check            # Rust cargo check\nmake fmt-check        # Read-only format check for frontend + Rust\nmake verify           # Local CI-like verification entry point\nmake gitleaks         # Scan current project files for secrets\nmake gitleaks-history # Scan Git history for secrets\nmake lint-frontend    # Read-only static check for the frontend\nmake test-frontend    # Run frontend tests\n```\n\n`pnpm install`\n\ntriggers the `prepare`\n\nscript and installs lefthook git hooks. Before a commit it runs staged Biome auto-fix, Gitleaks secret scanning, Rust format check, and commitlint; before a branch push it runs `make verify`\n\n; tag-only pushes are gated remotely by the release workflow's quality job. `make fmt`\n\nand `pnpm check`\n\nrewrite files; for read-only checks use `make lint`\n\n, `make lint-frontend`\n\n, or `make fmt-check`\n\n.\n\nBuild artifacts are located by default in `src-tauri/target/release/bundle/`\n\n.\n\n| Path | Purpose |\n|---|---|\n`src/` |\nReact frontend pages, components, hooks, schemas, and tests. |\n`src/components/` |\nPage-level components and reusable UI; finer component entry points are in `CLAUDE.md` . |\n`src-tauri/src/` |\nRust backend, Tauri commands, and local file and data capabilities. |\n`src-tauri/resources/` |\nBuilt-in providers, model pricing, status line scripts, and other resources. |\n`src-tauri/capabilities/` |\nTauri permission declarations. |\n`docs/` |\nUser manual, platform differences, and extended documentation. |\n`.claude/rules/` |\nPath-scoped maintenance rules for AI agents. |\n\nWhen filing an issue, please include as much as possible:\n\n- Operating system, Code Manager version, and Claude Code use case\n- Reproduction steps, expected result, and actual result\n- Relevant redacted log snippets from \"Settings -> Diagnostics -> View Logs\"\n- For development changes, the verification commands you have run\n\n[docs/user-manual.md](/maguowei/code-manager/blob/main/docs/user-manual.md): the complete user manual[docs/platform-support.md](/maguowei/code-manager/blob/main/docs/platform-support.md): platform support differences[docs/claude-code-best-practices.md](/maguowei/code-manager/blob/main/docs/claude-code-best-practices.md): extended best practices for Claude Code / Codex in this repo[CLAUDE.md](/maguowei/code-manager/blob/main/CLAUDE.md): the repository execution manual for AI agents[LICENSE](/maguowei/code-manager/blob/main/LICENSE): license\n\nMIT", "url": "https://wpnews.pro/news/code-manager", "canonical_source": "https://github.com/maguowei/code-manager", "published_at": "2026-07-15 15:01:59+00:00", "updated_at": "2026-07-15 15:28:30.887633+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools"], "entities": ["Code Manager", "Claude Code", "Tauri 2"], "alternates": {"html": "https://wpnews.pro/news/code-manager", "markdown": "https://wpnews.pro/news/code-manager.md", "text": "https://wpnews.pro/news/code-manager.txt", "jsonld": "https://wpnews.pro/news/code-manager.jsonld"}}