lomi wordmark
GitHubDownload lomi
Menu

Lomi guide Claude Code

Use Claude Code in Lomi

Run Claude Code alongside your project, local app preview and Git changes.

Download LomiClaude Code setup and sign-in
Lomi workspace showing a project explorer, code editor and running terminal.
Captured in Lomi: a project explorer, code editor and terminal.

Before you start

Set up Claude Code separately, then open the project you want it to work on in Lomi.

  • Install Lomi and open the local project you want to work on.
  • Install Claude Code and sign in using Anthropic’s setup instructions. Lomi does not install the CLI or sign in to your account.
  • Make sure the CLI is available in the local shell you plan to use. A Git repository lets you inspect or undo edits.

Use Claude Code setup and sign-in for current installation, supported-shell and authentication details.

Launch Claude Code in Lomi on macOS and Linux

On macOS and Linux, Agents looks for Claude Code in the local shell you selected, then opens it in a Lomi terminal at your project directory.

  1. Open the project

    Choose a project folder or repository in Lomi. The agent terminal starts in that project directory.

  2. Open Agents

    Select the + menu, choose Agents, and let Lomi check the selected local shell for installed command-line tools.

  3. Launch Claude Code

    Choose Claude Code and select how many terminals to open. If you installed it after opening the dialog, select Refresh installed CLI.

  4. Start with one clear task

    Ask Claude Code to explain the relevant files or make a specific change. Review its edits before keeping them.

On Windows, start it from a terminal

On Windows, Lomi cannot detect or launch agent CLIs from Agents. Install Claude Code using the vendor’s Windows or WSL instructions, then start it from a project terminal.

  1. Open a terminal

    In Lomi, select + and choose New terminal. Choose PowerShell, Command Prompt or WSL based on Claude Code’s Windows setup guide.

  2. Install and sign in

    Follow Anthropic’s Windows instructions for your chosen shell. Lomi does not install Claude Code or sign in to your account.

  3. Start the CLI

    At the project prompt, enter the command shown below to open Claude Code in the Lomi terminal.

Start Claude Code from the project terminalclaude

Lomi’s Agents detection and one-click CLI launch are not available on Windows. Lomi’s managed native-agent runtime is not qualified for Windows or WSL, so use a regular terminal and follow the CLI vendor’s platform guidance.

Follow Claude Code setup and sign-in for the current platform requirements and setup path.

Keep the coding loop in one workspace

With the CLI running, use other Lomi panes to run and preview your project, then review the diff in Git:

  1. Plan the change

    If the repository is unfamiliar, ask Claude Code to trace the relevant code and propose a small change before editing files.

  2. Run the app or checks

    Open another terminal for the project’s development server or checks. Both terminals stay in the same workspace.

  3. Preview locally

    When the server is ready, use + → New browser and enter its local address, such as the localhost URL printed by your development command.

  4. Review in Git

    Inspect the diff in Lomi’s Git view and run the project’s checks. Then stage and commit the changes you want to keep.

What this workflow includes

Lomi gives the CLI a local workspace with your project files, terminals and browser.

  • Claude Code’s prompts and replies stay in its CLI. Lomi provides the workspace around it; it is not a replacement chat frontend or a Claude Code IDE extension.
  • Claude access, sign-in, plan eligibility and API costs are handled by Anthropic. They are not included with Lomi.
  • This setup runs the CLI in a local terminal. It does not configure cloud delegation or unattended remote work. Claude Code’s own permissions and account rules still apply.

If Claude Code does not start

  1. Check the shell used by Agents

    On macOS and Linux, open a regular terminal with the same local shell selected in Agents. Run command -v claude to check that the shell can find the CLI. If it cannot, follow the vendor’s installation and shell-path instructions, then use Refresh installed CLI in Lomi.

  2. Confirm the project directory

    Check the terminal’s working directory before asking the agent to edit files. Use pwd on macOS and Linux or Get-Location in PowerShell. If it is the wrong project, open the intended folder in Lomi and start a terminal there.

  3. Start your development server separately

    An agent terminal does not automatically start your app. Run the project’s normal development command in another terminal, wait for its local URL, then open that address in Lomi’s browser. Use the actual port printed by the server.

For a two-agent workflow, see using Claude Code and Codex together, including when to keep edits in separate Git working trees.