myclaude v8.8.57

myclaude is an AI coding CLI. It starts fast, stays execution-first on real software tasks, and keeps product behavior anchored to myclaude even when the runtime is routed through compatible providers or gateways.

Study Guide

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

Current Highlights

• AI coding CLI identity with provider routing as explicit operator control, not the product definition
• Provider control center for saved profiles, current API environment, credentials, model slots, validation, and repair
• /mao bundled Codex execution through the active myclaude provider profile without a separate Codex login flow
• /team local team inspection with concrete provider-readiness and capability reporting
• Remote session surfaces that show the remote cwd, clear backend context correctly, and mark idle task boards as not currently running
• Proactive compaction plus reactive overflow recovery to keep long-context sessions usable

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 -y 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/myclaude-code@8.8.57/install.sh | bash -s -- 8.8.57

Quick Start

1. Run npx -y myclaude-code or myclaude
2. Open myclaude provider or /provider
3. Create or select a saved provider profile
4. Enter the API URL plus API key or auth token
5. Choose the primary, Haiku, Sonnet, and Opus model slots
6. Run /provider validate, then start the session 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 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.

CLI Entry Points

Version check:

myclaude --version
mycode --version
npx -y myclaude-code --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

myclaude auth login and myclaude setup-token are only for Anthropic account auth flows. They are not the provider-profile entrypoint.

In-Session Workflows

/provider manages saved profiles, current environment state, API URL, credential type, and model-slot routing from one place. Use it when you want to switch, validate, repair, or save the active route.

/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

/mao is the preferred Codex surface. It reuses the active myclaude provider profile directly, verifies /v1/responses reachability on the current route, and avoids a separate global Codex setup flow. /codex remains a compatibility alias.

/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

/team inspects real local team state from the active config root instead of giving 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 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. Use /team check for a concrete readiness report.

/retro runs a multi-round repo retrospective and upgrade loop guided by PRODUCT.md and ARCHITECTURE.md, with tisheng.md treated as historical context only when it still agrees.

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

Companion commands are still available and can either follow the current app provider or bind to a saved /provider profile independently.

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

Remote Sessions And Long Context

• Remote headers and status lines use the remote cwd instead of echoing the local machine path.
• Clearing a remote conversation clears the backend session before resetting the local UI.
• Idle task boards are labeled not currently running instead of implying active execution.
• Proactive compaction stays enabled for large sessions, and reactive overflow recovery remains available when a route still hits a hard context limit.

Compatibility And Routing Notes

• myclaude can import compatible profiles from ~/.ccjk/config.toml or ~/.ufomiao/zcf/config.toml.
• Changing the active myclaude provider profile writes the current selection back to those compatible config files.
• Proxy GPT routes stay on the Anthropic-compatible /v1/messages path by default. Only set MYCLAUDE_API_DIALECT=openai_responses when you explicitly want the Responses adapter for that gateway.
• Recommended saved profile pattern: gpt54-main for a validated gpt-5.4 route across the primary and inherited slots.
• Recommended saved profile pattern: gpt53-all when the route is validated for gpt-5.3-codex across the main thread and helper lanes.
• Recommended saved profile pattern: kimi-main or glm-main for provider-native routing with that provider's API URL and credential.

Package And Release Model

• Source repo: https://github.com/mycode699/myclaude-code
• Public package: https://www.npmjs.com/package/myclaude-code
• Public install entrypoint: npx -y 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

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.