Getting started on Kodelet

Usage

Sat, 12 Sep 2026 00:00:00 +0000

The built-in terminal UI and Web UI are the main ways to work with Kodelet. Both support ongoing conversations backed by the same daemon, with workspace execution handled by a runner.

Before starting, install Kodelet and configure a provider. Begin with terminal chat from your project directory, or start the managed daemon and open your browser.

Terminal chat

Start in the repository you want to work on:

kodelet chat

The terminal UI streams responses, shows tool activity, and saves conversations. A few useful controls:

Configuration

Sat, 12 Sep 2026 00:00:00 +0000

Most configuration surprises come from changing a setting on the wrong machine—or after the process that needs it has started. Begin with ownership, then choose a provider and profiles.

Daemon, runner, and client

Component	Owns	Configure it on
Daemon / server	Model requests, provider credentials, model profiles, conversation history, authentication, and host policy	The daemon host
Runner	Workspace files, shell environment, tools, recipes, skills, installed extensions, and environment profiles	The machine executing the work
Client	Server selection, client authentication, and display preferences	Your terminal, editor, or SDK host

The built-in runner shares the daemon’s machine. A standalone runner can execute elsewhere. Neither arrangement makes provider requests local-only: the configured model provider receives the inputs needed for inference.

Customization

Sat, 12 Sep 2026 00:00:00 +0000

Start with instructions before adding code. Use a recipe for a task you repeat, a skill for expertise the model should recognize, and an extension when you need executable behavior.

Workspace resources belong on the runner. Installing something on a remote client does not make it available to the machine doing the work.

Project context with AGENTS.md

Kodelet automatically loads AGENTS.md project context. Include the information a new engineer needs: repository structure, build/test commands, coding conventions, and operational constraints. Prefer concrete instructions over long descriptions of obvious code.

Automation

Sat, 12 Sep 2026 00:00:00 +0000

Build automation around saved conversations and explicit execution context. The daemon owns the work; clients can connect, provide guidance, and disconnect without becoming its lifetime manager.

Find and continue a conversation

All user-facing runs are saved in the daemon’s conversation store, including --result-only runs. Find the conversation you need:

kodelet conversation list
kodelet conversation list --search "migration"
kodelet conversation show CONVERSATION_ID --format markdown

Replace CONVERSATION_ID with an ID from the listing. Search matches conversation IDs, working directories, first messages, and summaries.