yo-code

yo-code is the working repository for the recovered CLI source tree imported from a previously nested local checkout.

This repository is being rebuilt into a development-ready standalone workspace:

• repo identity and docs are being rebranded to yo-code
• the local toolchain has been reconstructed around Bun and TypeScript
• local auth is being moved to provider-account storage instead of Anthropic OAuth
• user-facing product strings are being migrated in audited passes
• risky internal contracts are being preserved until they can be renamed safely

Status

The repository is usable for source inspection, incremental refactoring, and tooling recovery. It is not yet a clean open-source codebase:

• the source provenance is documented in SOURCE_PROVENANCE.md
• the current LICENSE reflects the imported code provenance
• legacy runtime contracts still exist inside src/

Quick Start

bun install
bun run check
bun run typecheck

Auth Setup

yo-code now uses local provider-account storage for Anthropic-compatible API keys.

Interactive:

bun run ./bin/yo-code
# then run /login inside the TUI

Headless:

YO_CODE_API_KEY=your_key \
YO_CODE_ACCOUNT_LABEL=primary \
YO_CODE_BASE_URL=https://api.anthropic.com \
bun run src/entrypoints/cli.tsx auth login

Provider accounts are stored at ~/.claude/yo-code-accounts.json with optional auto-rotation after 429 rate limits.

Repository Layout

yo-code/
├── bin/                Bun launcher entrypoints for the yo-code CLI
├── src/                Imported CLI source tree
├── docs/               Setup, runbook, feature, tool, and rebrand docs
├── assets/             Imported project assets
├── types/              Global type shims for reconstructed tooling
├── ARCHITECTURE.md     Codebase shape and subsystem notes
├── CONTRIBUTING.md     Contribution rules for this repo
├── DEVELOPMENT.md      Day-to-day development workflow
├── SECURITY.md         Security reporting guidance
└── SOURCE_PROVENANCE.md  Source provenance and legal context

Development Priorities

1. Keep the repo buildable and inspectable with the reconstructed root tooling.
2. Continue the rebrand on user-facing surfaces first.
3. Rename internal runtime identifiers only when the contract is understood.
4. Add validation and release automation once the runtime path is stable.

Validation Notes

• bun run check validates maintained repo-facing docs and rebrand-safe root metadata.
• bun run typecheck validates the reconstructed compatibility declarations.
• The auth/account store module loads successfully in isolation with Bun.
• bun run typecheck:full is currently a backlog command for the imported tree; it still fails because the recovered source snapshot is missing upstream generated modules and type surfaces.
• Full CLI boot still fails on missing recovered modules in src/tools/ and related generated runtime files. That blocker is separate from the new auth layer.

Core Docs

• ARCHITECTURE.md
• docs/AUTH.md
• CONTRIBUTING.md
• DEVELOPMENT.md
• SECURITY.md
• SOURCE_PROVENANCE.md
• docs/SETUP.md
• docs/ENVIRONMENT.md
• docs/RUNBOOK.md
• docs/REBRAND_AUDIT.md
• docs/COMMANDS.md
• docs/TOOLS.md
• docs/FEATURE-FLAGS.md