>_ LETCODE · USER MANUAL

LetCode User Manual

LetCode is an AI coding agent: it understands your project, edits code, runs commands and passes tests — from the desktop, the terminal or the browser. Built on a deeply re-engineered agent kernel, with models, tools and capabilities composed entirely through plugins. All mainstream AI models are supported.

Desktop App · macOS / Windows CLI · terminal & CI Web · browser Local-first · Multi-model v0.0.x

This manual covers: installation & startup, interface tour, core features, model configuration, command reference, security and privacy. Written for newcomers who have never used an AI coding agent — and for developers who want to run LetCode inside team pipelines.

What LetCode can do

Edit code

Understands project structure, coordinates cross-file edits, watches build and lint errors, and proactively fixes type mismatches and missing references.

Run commands

Executes shell commands in your project and watches output live: install deps, run tests, build, deploy.

Plan first

Plan mode explores, asks questions and proposes a strategy — you approve before it executes. Every change requires your sign-off.

Automate

Scheduled tasks, headless pipelines, multi-agent teams and messaging platforms — hand the repetitive work to the agent.

01Quick Start

Requirements

  • OS: macOS (Apple Silicon / Intel) or Windows; Web & CLI are cross-platform
  • Node.js: 18+ required for desktop & CLI (the only runtime dependency)
  • Model API key: a key for any supported model (Claude / GPT / Gemini / DeepSeek / Qwen etc.; local models need no key)

Installation

Option A: one-click macOS install (recommended)

Download the source package, then run the one-click script in your terminal. It handles environment checks, dependency install, build and install automatically:

# run in the project root bash install-mac.sh

The script automatically: checks and installs Xcode Command Line Tools → Rust → Bun 1.4.2 → installs dependencies → builds → packages with Tauri → installs into Applications. First run takes about 10-20 minutes; after that, double-click to launch.

Option B: build a release package (.app / .dmg)

# install dependencies bun install # run in dev mode (fastest way to see it) cd apps/examples/desktop-app bun run dev # or build a release package bun run build bunx @tauri-apps/cli@2 build

Artifacts live in src-tauri/target/release/bundle/ — drag the .dmg into Applications.

Option C: CLI / terminal

letcode "describe your task"
Tip:If the system blocks the first launch, right-click the app → Open, or run xattr -cr /Applications/LetCode.app to clear the quarantine flag (see FAQ).

Your first task

  1. Launch LetCode and pick a project folder as your workspace
  2. Add an API key for any supported model in Settings
  3. Type your first task, e.g. fix the token-expiry bug on the login page
  4. Watch the agent: read files → locate logic → edit code → run tests → show diff
  5. Approve or revert every change in the diff preview

02Interface Tour

Desktop workbench

The LetCode desktop app puts sessions, agent activity, files, Git changes, terminal and plans into a single window:

AreaWhat it does
Project sessionsSessions are saved per project — switch repos and resume anytime; create new sessions, open settings
ChatType tasks in natural language; the agent replies, asks and proposes plans here
Terminal / activityLive view of commands and results: test output, build logs, tool calls
Diff previewEvery file change shown as a diff — approve, edit or revert (checkpoint)
Files / GitBrowse workspace files and Git status to see what the agent is changing

Menus & preferences

  • New session: Ctrl/Cmd + N; Settings: Ctrl/Cmd + , (File menu on all platforms)
  • Bilingual UI: Settings → General → Language — switch English / 中文 instantly, persisted
  • Theme: deep-ocean developer theme, follows the system dark mode

Plan and Act modes

Plan mode only explores: it reads code, asks clarifying questions and proposes a strategy. Once you align, switch to Act mode and it starts editing files and running commands.

  • By default every file edit and terminal command needs your approval — you stay in control
  • For trusted setups, enable auto-approve and let it run the whole task on its own

03Core Features

Cross-project editing

LetCode first reads your project structure to understand how files relate, then coordinates cross-file edits. As it works it keeps watching lint and build errors, proactively fixing missing references, type mismatches and syntax issues. Every change has a checkpoint — undo the agent's work at any time.

Running commands

LetCode executes commands in your project terminal and watches output live: install deps, build, test, deploy, touch the database. For long-running processes like a dev server, it keeps working in the background and reacts to new output — compile errors, failing tests and crashes are caught immediately.

Rules and skills

Create a .letcoderules file in your project to define rules: coding standards, architecture conventions, deployment flows, testing requirements. CLI, desktop and editor extensions all follow these rules automatically. Skills load finer-grained behavior on demand, so the model follows your process for specific tasks.

Multi-agent teams

A coordinator splits complex tasks into subtasks and dispatches them to specialized agents — each with its own tools and context. Team state persists across sessions, so you can resume after interruptions:

letcode --team-name auth-sprint "Plan and implement user authentication with tests"

Scheduled tasks

Run recurring automation on a cron schedule: daily PR summaries, weekly dependency checks, repository health reports. Tasks survive restarts and don't depend on any terminal session:

letcode schedule create "PR summary" \ --cron "0 9 * * MON-FRI" \ --prompt "List all open PRs and their review status" \ --workspace /path/to/repo

Messaging platforms

Connect the agent to Telegram, Slack, Discord, WhatsApp, Google Chat or Linear: each thread maps to a full-context agent session, with access control:

# connect Telegram letcode connect telegram -k $BOT_TOKEN # connect Slack (webhook) letcode connect slack --bot-token $SLACK_TOKEN --signing-secret $SECRET --base-url $URL

Headless mode & CI/CD

Runs with zero interaction — perfect for scripts and pipelines: pipe input, JSON output, command chaining, straight into CI/CD:

letcode "Run tests and fix any failures" git diff origin/main | letcode "Review these changes for issues" letcode --json "List all TODO comments" | jq -r 'select(.type == "agent_event" and .event.text) | .event.text'

04Model Configuration

LetCode isn't locked to any model vendor. Add the matching API key in Settings (or environment variables) to switch — you can change models per project, anytime.

ProviderAvailable models
AnthropicClaude Opus / Sonnet / Haiku
OpenAIGPT series
GoogleGemini series
DeepSeekDeepSeek series
Qwen / Kimi / GLMQwen, Kimi, Zhipu GLM and other leading models
OpenRouter200+ models behind one unified entry point
AWS Bedrock / Azure / GCP VertexAll models hosted on the major clouds
Cerebras / GroqHigh-speed inference models
Ollama / LM StudioLocal models (no key, data never leaves your machine)
Any OpenAI-compatible endpointPrivate or third-party APIs
Tip:With local models (Ollama / LM Studio) there's no network call and no model cost — ideal when data boundaries matter.

05Command Reference

CommandDescription
letcode "task description"Run a task interactively in the terminal
letcode --json "task"Output structured JSON for scripts
letcode --team-name <team> "task"Run in multi-agent team mode
letcode schedule createCreate a scheduled task (cron)
letcode mcpManage MCP server connections
letcode connect <platform>Connect messaging platforms (Telegram / Slack etc.)
git diff | letcode "review"Pipe input — review changes

Common in-chat commands

CommandDescription
@file pathReference a project file in chat for precise context
@symbol nameReference a code symbol — jump to definitions & call sites
/skillsLoad skill packs that follow your workflows
/mcpConnect external tools: databases, browsers, internal systems
/agentsOrchestrate parallel sub-agent tasks
/shareShare a session with your team for seamless handoff

06Security & Privacy

  • Local first: runs fully local by default — code never leaves your machine; sessions and config stay on your device
  • Tiered approvals: reads, writes and command execution are authorized tier by tier; critical actions ask you first
  • Checkpoint rollback: every change has a checkpoint — undo anytime
  • Access control: messaging integrations support allowlists, limiting who can talk to your agent
  • Auditable: sessions record every step — task, tool calls, results; team plans export audits
  • Bring your own key: model costs go straight to the vendor — no cut, no resale
Note:Only when you explicitly connect a cloud model API is relevant context sent to that provider — the standard mechanism for all cloud models. For sensitive projects, use local models.

07FAQ

Blocked: "cannot be opened / unidentified developer" — what now?
Unsigned apps are blocked by Gatekeeper. Right-click (or Control-click) the app → Open → Open; or run xattr -cr /Applications/LetCode.app to clear the quarantine flag. Official distribution needs an Apple Developer signature and notarization.
Which models are supported?
Anthropic Claude, OpenAI GPT, Google Gemini, DeepSeek, Qwen, Kimi, GLM, plus OpenRouter, AWS Bedrock, Azure, GCP Vertex, Cerebras, Groq, Ollama, LM Studio and any OpenAI-compatible endpoint. See the Model Configuration chapter.
Does my code go to the cloud?
Not by default. LetCode runs locally — your code stays on your machine. Only when you explicitly connect a cloud model API is relevant context sent to that provider; with local models (Ollama / LM Studio) nothing leaves your machine.
First build is slow / network errors?
Rust's first compile takes about 3-10 minutes, which is normal. grpc-tools postinstall may occasionally fail on the network — just re-run bun install.
How do I switch the UI language?
Settings → General → Language — switch between English and 中文, applied instantly and persisted.
Can I deploy it privately?
Yes. Deploy on your own servers or a team intranet; no seat fees, no hidden charges.

08Appendix · Tech Stack

For developers who want to re-engineer or contribute:

ComponentTech
Desktop shellTauri 2 (Rust)
FrontendNext.js (webview)
RuntimeBun sidecar (self-contained letcode-cli binary)
Core SDKMulti-package: shared / llms / core / agents / ui / sdk
ThemeDeep-ocean palette; edit sdk/packages/ui/theme/palette.css + tokens.css, then run generate:theme
Feedback:Feature requests and suggestions are welcome. This is a demo site — official releases govern.