Lime

An agent that finishes the work

An open-source full-stack AI agent for Desktop and CLI/TUI. Code, research, create, and work with files — with tools and results you can review.

Website · Get Desktop · Documentation · 简体中文

Start with a real task

Bring a repository, a folder of references, an error, or a brief. Give Lime a goal and boundaries. It can read context, use the tools you enable, make changes, and leave an output you can inspect and continue.

Model and media capabilities depend on the configured provider and tools. See the feature map for current ownership and verification scope, and task guides for concrete examples.

A workflow you can review

These are brand illustrations. The documentation describes the product's actual controls and workflows.

Quick start

Desktop

Download the macOS or Windows installer from Releases or the download page.

On macOS, you can also use Homebrew:

brew tap aiclientproxy/tap
brew install --cask lime

CLI/TUI

Requires Node.js 18 or newer. The launcher installs the payload for macOS arm64/x64, Windows x64, or Linux x64 GNU. It includes the local App Server; Electron is not required.

npm install -g @limecloud/lime
lime --version
lime

Run a single task or request structured output:

lime exec "review this diff"
lime exec --json "review this diff"

Your first task

1. Configure a provider, model, and credential; check that the connection works.
2. Choose a project directory and the required file, terminal, and tool permissions.
3. Describe the goal, relevant materials, constraints, and completion criteria.
4. Start with a plan when useful, then inspect file changes, command results, and outputs.
5. Request a focused revision or continue with the next step.

Models, tools, and control

Lime hosts the agent workspace; it does not supply AI models. Choose your provider and model, connect MCP tools as needed, and use Skills for repeatable procedures. Available capabilities depend on the provider, tool connection, and execution environment.

Project files, history, and configuration are local by default. Content needed for remote model or external-tool requests is sent to the service you select. Grant permissions for the current task and review actions that change files or external state.

Provider credentials default to user-restricted files without Keychain password prompts. See credential storage for paths and explicit keyring settings.

Web search API endpoints

Set these optional variables in the environment that starts Lime or its App Server. They affect the local bing_search_api and google_custom_search tools; model Provider endpoints are configured separately. Unset or blank values use the vendor addresses. Overrides must use HTTP or HTTPS and return the corresponding Bing v7 or Google Custom Search JSON format.

Choose an endpoint you trust to receive the search query and the provider credential. Invalid endpoint values fail that provider and continue through the existing search fallback chain; an endpoint override does not change the required request or response format.

Cloud computers

Choose Cloud from the composer's execution menu, or open Settings → Cloud desktops, to purchase, bind, or connect your own persistent Linux computer. After a verified ECS purchase, setup selects that exact computer and observes its startup. You can then install the runtime or rebuild a connection to an existing or restored environment. An unknown purchase result stays attached to the original operation for inspection.

For a first purchase, choose a region and authorize Alibaba Cloud in your browser. Lime prepares the official CLI if needed. Without a purchase template, you can authorize Lime to compare available 2-core, 4 GiB Linux options and prepare a dedicated network, without entering image, instance type, VPC, switch, security group, or SSH key details. Network preparation does not purchase a computer; ordering requires a live quote and separate fee confirmation. Reopening setup inspects the original preparation instead of creating another one. The dedicated network is reusable and remains after instance release.

Before an ECS purchase, Lime downloads and caches the matching official runtime, verifies its size and SHA-256, then prepares temporary distribution in your own private OSS. No package URL, bucket name, or access key entry is needed. This preparation happens before purchasing the computer; temporary storage and traffic are billed to your cloud account. After the last installation finishes, Lime cleans up the package object and empty bucket.

Failed preparation blocks the order. Users bringing their own environment can explicitly choose to connect it or supply a trusted custom package. Restoring a saved system image reuses its installed environment without preparing a new runtime package. An expired quote, a closed page, or a changed purchase context prevents a late response from submitting an order.

First installation on ECS uses the official runtime matching your Lime version. After you approve system installation, Lime prepares desktop dependencies and shows actual stages, received package bytes, and elapsed time. If that release is unavailable, no cloud installation command is sent; retry explicitly or select a trusted package under advanced options. Keep Lime running after closing the installation panel. After restarting Lime, use Continue original operation to resume inspection.

The cloud computer downloads and verifies the runtime over HTTPS. Control requests use your Alibaba Cloud authorization and Session Manager; installation services listen only on the computer's loopback interface. After your installation or reconnection consent, Lime configures connection rules for your current public address on its dedicated network and removes old address rules. No IP or port entry is needed; custom networks remain under your control. A successful installation saves the task connection encrypted. Existing managed environments can rebuild connections without reinstalling. Installation success does not establish that model tasks, applications, or restored logins have been verified.

The remote desktop stays collapsed by default. Choose View desktop to open the read-only viewer; collapsing it closes the display connection while the task connection remains available. Computer Use actions require their own authorization.

The cloud window checks its own model catalog. If it has no visible chat model, choose Connect model to open that computer's model settings. Returning to the task checks the configuration again; existing configurations do not repeat this setup. A catalog check does not make an inference request or verify model connectivity.

Expand Reuse a local model connection in the local Task connection panel to select an existing connection and authorize copying its API key to that computer. The cloud computer stores it persistently for its window and independent CLI; model charges belong to the selected model service. Interrupted delivery resumes the original operation without automatically creating another connection. Both runtimes must include model connection delivery. Ordinary configuration exports exclude actual API keys.

In Backups, choose Restore a saved environment, authorize your account, and select a private system image. Lime pre