First use: identify the prompt before typing

Follow the Ubuntu walkthrough or platform installation guide. The sequence is install, configure a model, launch chat, submit a task, then verify the artifact. A system prompt accepts commands; accept / decline: asks for license consent; activate offers an optional background service; only koder > accepts chat tasks. Skipping activation retains foreground chat. Enabling activation does not launch chat.

On Ubuntu/macOS, run "$HOME/.local/bin/koder" setup if needed, then "$HOME/.local/bin/koder". These full paths work before PATH refreshes. On Windows, reopen PowerShell and use koder setup, then koder. See the installation recovery steps.

This release checks for missing task output and website handoff evidence. Read Task results and recovery and Website delivery. The website Skill follows its applicable requirements, planning, layout, implementation and verification stages; existing off choices remain effective.

30-lesson hands-on and developer course · Browser classroom · Practical labs

Start here: installation, first task and feature navigation

0.5.19 includes computer care, installed-app access and the Windows disk-inspection fix. Start with the feature and tutorial map.

Current version: 0.5.19. Start with release changes, input and provider diagnosis and independent terminal tasks. The complete guide below retains existing workflows. Native Windows and authenticated-account limits are explicit in the release notes.

Older updaters can reject this package above their 100 MB limit. Run the current official installer once to upgrade in place while retaining configuration and history; see the migration guide.

This version includes default-on Headroom context optimization and separate history-compaction controls. This guide targets 0.5.19. The eight linked terminal text exports match this version; historical exports are excluded from the current package.

Koder CLI complete user guide

Version: 0.5.19. Check koder --version; older installations may have different behavior. Native Windows and real-account checks are recorded separately from local regressions.

1. Install in the right terminal

Use the matching Windows PowerShell, CMD, macOS, Linux or WSL instructions in Installation. Download this release from KarmenLoop/koder-cli on GitHub. Read the installed EULA and privacy documents before accepting. Personal noncommercial use is free; commercial use and organizational distribution need separate written authorization.

Normal installation does not require changing the machine-wide PowerShell execution policy or disabling security software. accept accepts the license; it grants no computer, mailbox or synchronization permissions. Default local task memory and external access have separate controls. A network delay, a canceled installation and an OS policy rejection are different conditions. The installer reports its stage and download progress; keep the exact error for diagnosis.

2. Connect your own model

Run koder setup. Choose the provider, exact account region and product, model ID, protocol and endpoint issued for your API or plan. A website subscription is not automatically API access. Gray provider entries are unavailable; switching billing routes is not a recovery method. Koder's native engine is the default; the optional fallback remains separately disabled.

Use an environment-variable reference when you want a saved profile without saving the key value:

koder model set --model ACTUAL_MODEL_ID --base-url OFFICIAL_API_BASE --protocol openai --key-env MY_PROVIDER_KEY
koder model test
koder model test --tools

Supply MY_PROVIDER_KEY through your shell's protected secret input or CI secrets; the example names a variable, not a key. --key-stdin is a separate configuration path that saves the supplied key in the local model profile. Do not use that path if you require an environment-only key. Never paste a key into a task, command argument, screenshot or issue. A one-shot environment configuration can use KODER_MODEL, KODER_BASE_URL, KODER_PROTOCOL, KODER_API_KEY, KODER_CONTEXT_WINDOW and KODER_MAX_OUTPUT; use limits the provider actually supports.

model test has a ten-second overall diagnostic budget and no inference retries; it checks text or a harmless tool round trip. A normal task has a different inference budget. A diagnostic failure cannot establish whether an account's plan is valid without a real authorized account check.

Context limits and automatic compaction (0.5.1)

Open koder setup or /setup and choose Context and output. Model window and output limit asks for the window, then the output ceiling, preserving the model, endpoint and credentials. Use the limits actually supported by your model, endpoint and account. Separate menu items control automatic compaction, trigger and target percentages, preferred recent turns, and reset. Compaction preferences are available before a model is configured.

koder context status
koder context set --trigger-percent 85 --target-percent 60 --keep-turns 6
koder context set --context-window 128000 --max-output 8192
koder context off
koder context on
koder context reset

The window values above are examples. Automatic compaction defaults to on, with an 80% trigger, a 60% target and four preferred recent turns. Recent turns remain subject to the model window. In chat, use the matching /context commands to change settings and inspect the last request's estimate. Estimates include input, tool definitions and output reserve; they are not billed tokens.

reset restores only compaction preferences, retaining model limits and Headroom settings. off keeps history for requests while Headroom and necessary protocol restoration remain independent. Requests that cannot fit the hard window report CONTEXT_BUDGET_EXCEEDED and retain saved history and original receipts. See Context limits and automatic compaction for the full walkthrough, named models, environment variables, last-request fields and save failures.

3. Keep every project in its own folder

New website, presentation and app creation tasks launched without an explicit workspace use a new folder under Koder Projects in the user's home directory. Existing projects are reused. An explicit -w always selects that existing workspace. Project files do not belong in Koder's program installation.

koder project create "Studio Site" --kind website
koder project create "Quarterly Review" --kind slides
koder project create "Studio App" --kind app
koder project list --json
koder project status
koder chat -w /absolute/path/to/existing-project

Inside the current chat, /project create "Another Site" --kind website creates and selects a separate project; /project open "/absolute/path" returns to an existing one. Switching closes the idle session and rebuilds it for the chosen workspace. Named collisions are rejected instead of merging files. Project metadata lives in .koder/project.json; it contains a project identity and path, not API credentials or a copied conversation.

4. Understand conversation isolation

The displayed session name default means the default session of that canonical workspace, not one global conversation. The same workspace and session can continue their saved history. Different workspaces and named sessions do not inherit one another's task transcript or automatically captured task facts. Explicitly managed shared notes are a separate feature and retain their declared scope.

koder ask "Continue this project's task" --session release
koder ask "Start a separate investigation" --session investigation
koder ask "Start fresh in this project" --new
koder ask "Use no saved task history" --no-memory
koder memory show --json

Conversation storage is in the user's private Koder profile, indexed by canonical workspace and session. It is not put in the public website output folder. “Workspace isolation” describes the identity boundary; it does not mean every private record is physically inside the project. Old records are retained. Do not delete the whole profile to solve a context problem.

5. Use scripts and pipes deliberately

An explicit ask or run prompt does not wait for unrelated stdin. Add --stdin when you want to attach pipe contents. With no prompt, stdin supplies the task. Input must finish within the configured deadline; partial input is rejected before a model call.

koder ask "Explain the current project"
printf '%s\n' 'Build output to inspect' | koder ask "Summarize this" --stdin
cat task.txt | koder run
cat slow-report.txt | koder ask "Inspect this" --stdin --stdin-timeout 30

PowerShell: Get-Content -Raw .\report.txt | koder ask "Summarize this" --stdin. CMD: type report.txt | koder ask "Summarize this" --stdin.

The default complete-input limit is five seconds, configurable from 0.01 to 3600 seconds with --stdin-timeout. Input is bounded at 400,000 bytes. A producer that never closes is an input error, not an API failure. Explicit prompts no longer need </dev/null to work around an open pipe. Large or incomplete input is not silently submitted as a truncated task.

6. Choose Ask, Agent and language

koder ask answers without proposing file edits or commands. koder run performs a task using the available tools and original approval policy. koder starts chat. Use --mode plan, code, execute, report, enhance, minimal or standard when appropriate; a mode is not a new permission grant.

koder ask "Explain the architecture" --lang en
koder run "Repair the failing check" --lang zh

--lang applies only to this invocation and reaches the model as an explicit response-language instruction. koder lang en saves a preference; /lang en changes the current chat. Code, identifiers and explicitly requested quotations retain their content. A provider may still fail to follow an instruction; that is distinct from omitting it from the request.

7. Approve operations by scope

Smart approval handles recognized low-risk checks and ordinary project edits. Sensitive or unknown effects ask for approval. Always allow applies to its recorded scope. --approval auto|ask|full|deny chooses the policy for a run. --yes does not override explicit deny, collect a password, grant OS accessibility/recording permissions or approve email and production publication. Full mode is not an operating-system permission bypass.

Inspect the exact target, command or diff before approving. An unknown result is not success; verify the state before retrying a send, payment or deployment. Repeated command approval and missing Windows OS authority are separate problems.

8. Review, fix and test

koder review
koder fix "Repair the login failure" --check "npm test"
koder fix --check "npm test" --attempts 3
koder test

fix needs a description, a check command or explicit input. --attempts accepts 1–20; --timeout is a positive check deadline up to 86400 seconds. The missing-input message includes a usable example. A check may run a project's code; use the normal execution approval and the project's actual dependency/setup instructions. A green narrow check is not proof that the whole application or installer works.

9. Compare three directions before building

New website, presentation and app tasks use three real HTML directions. Compare layout, content organization and interaction, not just colors. Open the local browser review, switch tabs or compare all, choose a direction and leave a rating and comments. A rating below 3 requests revision. A confirmed existing design, small fix or explicit skip avoids unnecessary exploration.

Consequential choices can use 2–6 step diagrams with tradeoffs. Browser feedback returns to the current Koder task; it does not submit a task or grant execution/upload authority. A PPT preview represents sample slides and narrative order; an app browser prototype is not native-device acceptance. See Visual workflow.

10. Keep a live companion preview

Use /preview in the current chat. Static pages use the local preview; frameworks attach to an already started, ready loopback development URL. Approved project writes or startup results can open the companion browser automatically. /preview auto off disables that behavior.

Preview does not install dependencies or start arbitrary scripts. Existing development-server HMR remains intact. Static refresh preserves active input or asks the user to refresh. Native apps need their simulator or device. The preview owner stops only its own resources. See Mail and live preview.

11. Use the bundled browser and design methods

Ask Koder to inspect or test a page. The Agent can use skill_catalog to find the browser workflow, then skill_read with ecosystem:agent-browser:core. The core guide, references, three starter templates and Apache-2.0 license are pinned locally from Vercel's agent-browser repository. They are on-demand method files; this update does not install the external executable or a browser binary.

Koder first inspects the actual computer driver and authorized target, captures a fresh snapshot, acts with that snapshot's element identity, and observes the result. COMPUTER_DRIVER_MISSING means the host driver is not connected. Upstream @eN refs and Koder element IDs are different. Authentication state, cookies, sending and uploads require their actual authorization. Unknown results are checked before replay. Reference templates are never automatically executed.

The existing ecosystem:skills:frontend-design content and license already match the verified Anthropic upstream commit. It remains built in; unrelated skills were not repinned. Skill methods do not override user instructions or tool permissions. Loading every manual into every turn is unnecessary: catalogs are searched and resources read only when needed.

12. Deliver an H5 project atlas

At eligible project handoff, Koder creates a standalone H5 map from real project files. Search files, expand groups, inspect sizes and local reference candidates, and export its structure JSON. Keep the map with the delivered project.

Hidden/private paths, credentials, dependencies, symlinks and generated review/delivery folders are excluded. A limit or unreadable scope must be visible. The map is neither a fabricated architecture nor a semantic call graph or functional test. Inspect filenames and structure before sharing. /visuals deliver requests a fresh map explicitly.

13. Connect your own Netlify site

The intended flow is Connect → choose site → inspect output → authorize draft upload → review preview → separately approve publication. Use /netlify in chat or the Applications and MCP settings group.

Koder's browser login is gray until its own OAuth application is configured. Protected PAT entry is a separate path. Binding a site does not authorize upload. Drafts upload content externally and may be publicly accessible. A saved draft grant is restricted to one exact workspace/output folder/site. Production publication is separate, with identity readback. Unknown writes are reconciled rather than automatically repeated.

The first adapter accepts prebuilt static output. SSR, functions and native bundles need their real adapters. Koder-managed membership hosting, quotas and billing are not configured; a Koder membership cannot silently change a Netlify plan. See the complete Netlify workflow.

14. Mail, apps and external messages

/setup mail supports the available 163, QQ, Gmail, iCloud, Microsoft and Spacemail presets, with actual availability and authentication requirements shown. Custom receive-only POP3 with TLS/STLS is supported where the server provides it. Microsoft OAuth remains unavailable until configured. Use the exact server and port table in Mail and live preview.

Connecting an account is not sending authorization. Advertising, verification-code and automated messages are not automatically replied to. Verification codes remain outside model context. Model access to selected mail and actual sending have their separate consent. Classifications are estimates; inspect important mail yourself. An uncertain send is checked instead of resent.

15. Skills, resources, reverse analysis and suggestions

Use skills and resource-library results on demand. Downloaded pages, skills, archives and templates are untrusted reference data; they do not grant installation or execution authority. Resource rights remain with their sources. A privately licensed archive is not made redistributable by renaming or encryption.

Koder Reverse is a first-party static subset with explicit coverage, not an accepted complete replacement for every REA engine. It does not execute the target. See Koder Reverse and REA.

Context suggestions are optional editable drafts. Choose one, change it or type your own; selection is not submission. /prefill, /prompts and /suggest off remain available. See Prompt prefills.

Native capabilities and MCP commands (since 0.5.2)

Use the capability inventory to distinguish Koder implementations, third-party runtimes and remote services, then inspect the tools your project needs:

koder mcp capabilities --json
koder reverse status
koder reverse project ./src --json
koder mcp presets --json
koder mcp doctor codegraph

Replace ./src with your project's JS/TS source directory. The Agent can also use native code_graph for imports, imported_by and symbols, then read the source to check the candidates. This path reuses the Koder Reverse Worker without starting another MCP service, installing a graph database or executing target code. It provides bounded lexical navigation, not a complete call graph. Python and advanced Cypher remain with optional CodeGraphContext.

mcp capabilities does not connect an account or establish which tools are mounted and authorized in the current task. Windows-MCP, REA, SolidCraft, the official MCP SDK and remote services retain their own ownership. The 23 related local tests passed, including a scripted model's graph→source read→continuation path. No paid model or Windows GUI was run in this round. See Capabilities and MCP boundaries for the complete scope.

16. Updates, recovery and privacy

Installed interactive chats check the official feed in the background and wait for an idle, verified handoff. Active tasks and unfinished drafts delay replacement. A changed license needs review. koder update auto status|on|off controls automatic checks. A failed preparation keeps the current conversation available; do not run a second installer over an active update.

A native Windows installation/restart check is separate from source-level tests. Back up the user's project and private profile using the documented paths before a manual migration. Never copy API keys or execution authority into shared memory. Read koder privacy consumer, statement, agreement, desktop or sources for the full installed notices.

17. Diagnose a failure without exposing secrets

An invalid model or parameter reports HTTP status, host and a bounded, redacted provider reason when a supported JSON error supplies one. It does not dump response bodies or authorization headers.
A diagnostic network failure uses a short single-attempt budget. Normal task transport has separate limits; downloads have their own much longer completion setting. Do not confuse these timeouts.
CONTEXT_BUDGET_EXCEEDED means configured input/history/tools do not fit. Use the model's actual context/output limits; an optional numeric budget receipt contains counts, not conversation text. Catalogs load on demand to reduce fixed overhead.
Incomplete streams or tool calls remain unexecuted. After a verified file action followed by a model failure, resume the model reply instead of replaying the action.
A memory isolation warning may use the disclosed temporary RAM fallback. It does not mean administrator privileges will fix the model's HTTP 401.

Usage and invalid configuration return exit 2. Task/check failures use a nonzero result; successful commands return 0. Treat every nonzero status as unsuccessful in scripts rather than relying on the wording of the message. Preserve version, command, stage and redacted final lines for support.

18. Learn and find every command

The interactive coach has 30 lessons, with PowerShell, CMD, macOS and Linux editions. It uses a disposable practice project and a scripted coach, so the tutorial needs no paid model call. koder learn --print gives the text edition; koder help COMMAND shows current usage.

The complete generated command reference covers every documented command and global option in this beta. The version, lesson count and actual configured model are distinct values; there is no universal default paid model or implied subscription.

For a bug or licensing inquiry, koder feedback or koder business provides info@karmenloop.com. Nothing is sent automatically. The official site is karmenloop.com.

Download the eight text editions

Structured reviews and headless Linux

koder review --format json follows up at most once when a successful model answer has no structured findings. If it still cannot parse a complete review, it exits 3 with REVIEW_UNPARSED; CI must not interpret that as a clean review. API failures retain their failure exit and are not retried by this follow-up.

On Linux, the application/connections host requires secret-tool (commonly supplied by libsecret-tools), a DBus session and an unlocked Secret Service such as gnome-keyring. A headless container without these cannot use protected connections. Koder does not install system packages or weaken credential protection automatically. Process-only memory does not satisfy the protected host requirement.

For a model configured only through environment variables, model list and model context inspect that model; change its limits with KODER_CONTEXT_WINDOW and KODER_MAX_OUTPUT. update auto status reports both a saved setting and the effective KODER_AUTO_UPDATE=0 override when present.

Remote references are off by default. koder resources search "keywords" --remote authorizes that command to send keywords to karmenloop.com. Set KODER_REMOTE_RESOURCES=1 to offer these tools to the Agent; set it to 0 to block them. Local private searches never fall back to the remote service.

Headless operation and evidence checks

CLI contracts define stdin, unanswered clarification, temporary approvals, unchanged history after a rejected pre-response request, and exit codes. Preserved blind prompts separate deterministic runtime checks from real model grading. Unparsed reviews and unsupported writing attribution exit 3; they are not clean CI results.

Writing and project delivery checks

See Quality checks for exact behavior and limits. A failed writing or delivery check returns exit 3, preserves files, and reports what remains unverified. It does not masquerade as an API failure. Project inspection is available without a model:

koder project check --kind service --json -w /path/to/project
koder project check --kind website --json -w /path/to/site

Use the existing authorized test command separately. A test file's presence does not prove it passed. Model presets now report catalog-derived selectable and temporarily unavailable counts; check your own account separately.

Windows interaction and code graph context

Read Windows-MCP and Code Graph setup for current-terminal setup, platform/launcher checks, workspace binding, actual calls and disconnect behavior.

Actual Windows-MCP and Code Graph acceptance: tested platforms, native prerequisites and remaining limits.

Feature quick reference

Use koder skills list and /skill for portable methods. Add input while the agent works; Setup selects steer or queue. Use /harness deep-research for research, or koder harness off for baseline behavior. App operations keep existing grants and driver limits. Missing persistent experience owners produce NO_ENTRY.

Skills · Input and Setup · App use · Harness · Changes and limits

Residency and mail inquiries

After installation, verify koder --version reports 0.4.23, then configure a model with koder setup. Optionally run koder activate; inspect with koder status and disable with koder deactivate. Residency does not grant tool permissions. Mail, calendar and browser history are off by default. Setup controls quiet hours, reminder limits and visible sources.

Bind mail in Setup using masked authorization-code input. Separately enable /mail model on and /mail inquire on with their consent phrases. Related incoming mail can offer choices; a choice creates a draft, and sending still requires final preview and confirmation. Background mail checks also require mail visibility in resident settings. Advertisements and verification codes are excluded from inquiries.

Complete resident guide · Complete mail guide · Changes and unverified paths. All 30 lessons and eight text editions remain; start with koder learn.

Existing workflow guides

MCP and Skill compatibility

Catalog, switches, dependency checks and transport setup · Inventory · 0.4.23 changes.

Model updates: Setup → Model supports automatic discovery, manual refresh and an off switch. Complete guide.

Automatic update guide: activation now starts the updater in the current chat; natural-language controls are supported.

Live input and diagnostics: steering, queueing, cancellation, editable prompt choices and local logs.

Command duration and saved progress

Connect GitHub and host a project

Run koder github connect, or choose Setup → Apps / MCP → GitHub. Bind your own token to read repositories, create a private repository, commit selected files, edit README or repository copy, and open a draft PR. Each write needs approval; uncertain results require reconciliation. Follow the complete guide.

Move devices and learn

Run koder migrate or use Setup. Follow the migration guide, verify the imported profile, then reconnect accounts. Open the 1,800-lesson Chinese classroom for hands-on and developer tracks; the original 30 English lessons remain available. Browser notes can be exported.

Retained session controls: compact input and Todo

The default dock uses two rows, or three with a Todo summary. Keep typing while work runs; Enter uses the selected steer/queue mode. Ctrl+T expands Todo, /todo prints the full list, and /help opens shortcuts. Press / in empty input and Tab to fill a draft. Adjust the footer in Setup → Session interface and apply changes with /reload-tui. User and developer guide.

SolidCraft CAD

Run koder cad enable, koder cad verify and koder cad test in the project, then start chat. Save the editable design each turn and reopen it explicitly next time. See the SolidCraft tutorial for dimensions, exports, permissions, recovery and platform status.

Awesome LLM Apps

AI application workflow tutorial: 146 pinned offline references, seven adapted methods, local retrieval and quote verification. Run koder llm-apps status. Disable through Setup → Skills. Example dependencies and accounts require project-specific configuration.

0.4.21: Skill discovery and child execution

Walk through discovery and delegation: source-scoped search, pinned installation, same-task continuation, model and effort selection, shared budgets and cancellation.

0.4.22: Website requirements and design

Default website intake, 84 offline reference documents, original approval and implementation workflow. Hands-on guide.

0.4.23: Website delivery and project anchors

Use the default Fullstack Web Delivery Skill to clarify requirements, retain project direction and implement or repair a website. Hands-on guide.

0.4.24: Document questions

Use the default PageIndex Skill to navigate local documents, read selected sections and verify citations. Hands-on guide.

0.5.0: Invocation, OCR and professional roles

Read the complete execution guide. It covers installation checks, local OCR, role selection, FIFO concurrency, headless completion and platform limits.

Model-specific thinking and output limits

Ubuntu 24.x full-runtime and desktop setup.

Private credential input

Version 0.5.14 supports hidden credential input, existing account bindings, Ubuntu private login filling and native sudo prompts. See Credentials and private login input for the workflow and platform limits.

Recover an interrupted session (0.5.19)

In chat, use /reconcile to inspect pending calls. After checking the actual target, use /reconcile checked <call-id>. Original UNKNOWN receipts and normal approval requirements remain intact; nothing is replayed. Exact ESC/Escape input cancels without starting a model turn at idle. See session recovery.