Questions people ask first

Is this another chat client for Claude?

No. The model stays the one you already pay for and already trust: Claude, Codex, Gemini, or a local one. LogiShell is the door that model reaches your work through, and the place that work is collected: projects, machines, terminals, agent sessions, documents, boards, and the record of why something was done the way it was.

The test we apply to every feature is not "is this a nice screen" but "are there now fewer places where your work lives?"

Do you read my API keys or my provider credentials?

No. You install Claude Code, Codex or the Gemini CLI the usual way and sign in to them the usual way. The shells LogiShell opens do not inherit the runner's own credentials either.

Does my code have to move to you?

No. A connected machine is your own hardware. Files, terminals and agent sessions live there. Your git remotes, your CI and your repository policy are yours and are not touched.

Does anything have to be open to the internet on my machine?

No. The node dials out to the control plane. There is no incoming port, which is also why the usual cause of "it does not appear" is an outbound proxy and not a firewall rule you forgot.

Pairing a machine gives it work straight away?

No, and this is deliberate. A paired machine is pending and the hub answers nothing but /healthz for it until a signed-in person approves it in Settings → Devices. Anyone holding a pair code can pair, so the last word belongs to a person, not to the code.

Can my agent use LogiShell without an account?

Yes, for the public things. The public MCP door needs no sign-in:

claude mcp add --transport http logishell-public https://mcp.logishell.com/mcp/public

It reads this documentation, checks the platform's health, and can inspect any other MCP server. Your projects, machines and board are behind the personal door, which signs you in with OAuth and creates the account on first use. Both doors, with every tool, are on the MCP page.

How do I connect one more machine?

One command on that machine, then one approval from you. The command and the code in it come from Settings → Devices → Pair new compute, and the steps for macOS, Linux and Windows are on Connect a machine. Nothing has to be reinstalled on the machines you already have.

If you also want to see its desktop, not only its terminals, that is a second step: See the screen of your machines.

The screen of my machine is slow or blurry

The browser view is VNC, which sends pictures of what changed. It is fine for opening a window and pressing a button, and it blurs on anything that moves. Check two things first: tailscale status on the device you watch from (direct is fast, relay adds a hop), and the load on the machine itself. If you need smooth motion, add a video stream next to it. The numbers we measured and the steps are in Speed and quality.

My machine lags while my agents work

Almost always that is memory, not the processor. LogiShell watches it on macOS, Linux and Windows alike: a local model is not woken in the background when there is no room for it and leaves a minute after its last background call, the background work of LOG moves to another of your personal machines with a graphics card when this one is full, and heavy commands of your agents (type checks, tests, builds) wait in a short queue instead of all running at once. You can see which of your machines has room in the machines view, and an agent asks the same question before it places work.

Where are the reports my agents write?

In your account, each at its own address: https://app.logishell.com/artifact/<id>. The agent gives you the link when it saves the document, and artifact_list returns all of them, so "show me my artifacts" is a question you can ask any agent connected through the MCP door. They are private to you and keep their earlier versions. How it works: Get an agent's report as a link.

What is LOG?

LOG is the assistant and the mascot: a yellow cube with a face. It has a working memory of what you are doing, it can watch your terminals and speak when something is worth your attention, and it can be asked directly. It is part of the product, not decoration: the face is how you can tell at a glance whether it is thinking, searching, acting or waiting.

Can LOG type into my terminal?

Only through the consent gate, one approved action at a time. Watching a terminal and writing into one are different permissions. A write request names the exact machine, project, session, action and input, lands in your inbox, and only that exact request can be executed once approved.

Which parts run where?

Is there a command line?

Yes, one static binary, lsh. Bare lsh in a terminal opens a conversation in the current directory; in a pipe it prints help and exits, so nobody's script ever hangs in an interactive loop. Every verb is in the CLI reference.

Something on this page is not what I see in the app

Then the page is wrong. The feedback tool inside the product reaches the people who write these pages, and a note with a screenshot is enough.