myclaude v8.8.47

myclaude is an AI coding CLI. Its core job is simple: start fast, stay execution-first on real software tasks, and let you route the CLI through compatible providers without turning provider setup into the product identity.

Study Guide

For full user-facing usage and learning documentation, start in study/README.md.

Core

• AI coding CLI identity with provider routing as a capability, not the product definition
• Saved provider profiles with API URL, credential, and routing in one place
• Anthropic-compatible gateway support for direct API usage
• Native commands myclaude, mycode, and optional installed claude
• Release flow built around tracked dist/ artifacts and npm distribution

What This Release Achieves

• Official marketplace plugin skills now stay in the high-priority static listing during skill-search turns, so GPT/OpenAI routes can reliably see important installed skills on turn 0 and inside subagents
• Large inline SKILL.md bodies are compacted at runtime for GPT/Codex-family models while preserving hard gates, checklists, and execution-critical guidance
• Remote canonical skills now use the same compacted runtime path as local and plugin skills, reducing prompt bloat and lowering the risk of context-window overflows
• Added focused regression coverage for runtime skill compaction and official plugin-skill prioritization

Install

Requirements:

• Node.js 18 or newer
• macOS or Linux shell environment

Install globally from npm:

npm install -g myclaude-code

Run it once with npx if you do not want a global install:

npx myclaude-code

This installs the non-conflicting npm commands:

myclaude
mycode

Then run the built-in installer once to configure the native launcher, including the claude command:

myclaude install --force

After that, you can launch with:

myclaude
mycode
claude

One-line install:

curl -fsSL https://unpkg.com/myclaude-code/install.sh | bash

Install a specific version:

curl -fsSL https://unpkg.com/[email protected]/install.sh | bash -s -- 8.8.47

Quick Start

1. Run myclaude
2. Open the provider configuration flow
3. Create or select a saved provider profile
4. Enter the API URL plus API key or token
5. Choose the primary, Haiku, Sonnet, and Opus model slots
6. Start the session immediately with the active profile

This package is intended for users who want an execution-first coding CLI with explicit routing control when compatible providers or gateways are part of the setup.

On macOS, myclaude now avoids Keychain by default and stores local credentials in ~/.claude/.credentials.json so startup does not trigger system Keychain prompts. If you explicitly want the old Keychain behavior back, launch with MYCLAUDE_USE_KEYCHAIN=1 myclaude.

Commands

Version check:

myclaude --version
mycode --version
# available after running: myclaude install --force
claude --version

Provider/config entry point:

myclaude provider

Anthropic account login/token commands:

myclaude auth login
myclaude setup-token

Inside the interactive CLI, use /provider to switch a saved provider profile in one step. Each profile carries its API base URL, API key or token, and the effective primary/Haiku/Sonnet/Opus slot routing together. myclaude auth login and myclaude setup-token are only for Anthropic account auth flows; they are not the provider-profile entrypoint.

/provider
/provider list
/provider current
/provider save-current kimi-main
/provider adopt-current kimi-main
/provider validate
/provider repair
/provider use gpt54-main
/provider use kimi-main
/provider clear

Use /mao for first-party Codex execution through the active myclaude provider profile. This path reuses your current API URL and credential directly and does not require a separate codex login, a separate global Codex install, or a parallel Codex config flow. /codex remains as a compatibility alias, but /mao is the preferred command surface. Start with /mao setup: it verifies the bundled Codex runtime, the active provider profile, and /v1/responses reachability on the current route.

/mao setup
/mao review --background
/mao adversarial-review --base main auth and retry handling
/mao rescue --write fix the provider override bug and verify it
/mao rescue --resume apply the top fix from the previous Mao run
/mao status
/mao result

Use /team to inspect real local agent-team state from the active config root instead of getting a generic explanation. By default that is ~/.claude/teams, but it follows CLAUDE_CONFIG_DIR if you launch myclaude against a different config root.

/team
/team list
/team current
/team status myteam
/team show myteam
/team check

Typing agent teams at the start of a prompt now opens the same native /team flow instead of sending that phrase to the model as plain text. For external users, /team still requires local opt-in with --agent-teams or CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1, and the feature rollout gate must also be open. Use /team check for a concrete readiness report.

Use /retro to run a multi-round repo retrospective and upgrade loop inspired by karpathy/autoresearch. It treats PRODUCT.md and ARCHITECTURE.md as the primary control documents and uses tisheng.md only as historical context when it still agrees with those newer docs. By default it instructs the agent to carry a run tag plus an untracked .claude/retro/results.tsv keep/discard ledger and .claude/retro/latest.md working note so each round leaves behind reusable product memory instead of pure chat history. The loop now treats compatibility, stability, interaction logic, and reliability as explicit keep gates instead of optional afterthoughts.

/retro
/retro provider control center stability
/retro onboarding and route validation

Companion commands:

/girl
/boy
/bigdaddy
/girl provider
/girl provider list
/girl provider inherit
/girl provider use <profile>

Each companion can either follow the current app provider or bind to a saved /provider profile independently.

Recommended saved profile patterns:

• gpt54-main: gpt-5.4 as the primary model, with Sonnet/Haiku/Opus inheriting from that same stable route
• gpt53-all: gpt-5.3-codex for the main thread, subagents, and helper requests
• kimi-main or glm-main: provider-native routing with that provider's API URL and token

Compatibility:

• If ~/.ccjk/config.toml or ~/.ufomiao/zcf/config.toml exists, myclaude can import those profiles and follow the external active-profile switch
• Changing the active myclaude provider profile also writes the current selection back to those compatible config files
• For proxy GPT routes, myclaude now stays on Anthropic-compatible /v1/messages by default. Only set MYCLAUDE_API_DIALECT=openai_responses when you explicitly want the Responses adapter for that gateway.

Current gateway note:

• On the verified ttqq.inping.com route, gpt-5.4 is stable for the main thread
• gpt-5.1 is the current stable fallback for subagent and fast-helper slots
• gpt-5.3-codex may work intermittently, but this gateway sometimes returns upstream unauthorized errors for it

Release Model

• Source repo: https://github.com/mycode699/myclaude-code
• Public package: https://www.npmjs.com/package/myclaude-code
• Public install entrypoint: npx myclaude-code
• src/ is the development surface for new changes, while the checked-in dist/ bundle is the current shipped runtime artifact
• types/generated/ holds generated contract types that stay outside authored runtime source
• GitHub Releases publish installable archives plus install.sh
• npm distributes the same tracked top-level runtime entrypoints that power dist/cli.js, without shipping nested dist/ development artifacts, .map files, or .d.ts files
• npm run verify:source-build rebuilds the CLI from src/ into experimental-dist/ and smoke-tests the Node entrypoints as a structural guard
• dist/ is still the shipped artifact today, but release verification now requires both tracked dist/ integrity and a bootable source rebuild
• Trusted publishing is the intended npm release path so new tags do not require repeated local OTP prompts

Goals

• Remove startup dependence on Claude Code account login for normal provider-based use
• Make provider configuration feel native, direct, and routing-aware
• Keep installation simple through npm, npx, and the native installer
• Ship a reproducible release surface with verification around the checked-in runtime bundle
• Support real third-party gateways without hiding routing or credential state behind opaque defaults
• Keep src/ authored and readable instead of mixing build transforms into live source

Developer Verification

npm run validate:repo
npm run verify:dist
npm run verify:source-build
npm run check:source-purity
npm test
npm run check
npm run build
npm run package:release

• npm run validate:repo: checks package metadata, required tracked files, workflow presence, and tag/version consistency
• npm run verify:dist: smoke-tests dist/cli.js and dist/provider-setup.js
• npm run verify:source-build: rebuilds from src/ into experimental-dist/ and requires --version plus --help to boot under Node
• npm run check:source-purity: fails on inline source maps, compiler-transformed React output, generated stubs, or generated types inside src/
• npm test: runs packaging and release regression tests with Node's built-in test runner
• npm run check: full local verification gate used by CI
• npm run build: runs check and previews the publishable npm tarball with npm pack --dry-run
• npm run package:release: runs check and produces archives in release-artifacts/
• npm run rebuild:experimental: manual alias for npm run verify:source-build
• npm run rebuild:experimental:legacy: older reconstruction path kept for manual investigation

For source reconstruction work there is still npm run rebuild:experimental, and the older npm run rebuild:experimental:legacy path remains available for comparison. Both write only to generated paths. The plugin-based rebuild is now part of local and CI verification, but it still does not replace tracked dist/ as the shipped release artifact.

Package Focus

This repository is the release home for myclaude: an AI coding CLI that keeps execution quality and runtime discipline product-owned, while still giving you direct control over provider routing, credentials, and compatible gateway usage.