What LogiShell is

Work is scattered across memory, notes, agent sessions, and tasks of different size. LogiShell collects them into one system.

A block is not the goal. A block is the form: a contract at the seam (typed ports, abstract capabilities, a cost). Code, artifacts, databases, and people sit behind that contract. A person is a lane adapter.

The check for any feature: are there fewer places where work lives?

What you actually get

• A desktop (and a web IDE) where terminals, files, boards, and LOG live in one window.
• A local runner on your machine. Shells and agents survive a tab close. The cloud does not hold your PTY.
• Equal providers. Claude Code, Codex, Gemini CLI, and a key you bring yourself. LogiShell does not read their credentials.
• MCP doors. The same tools an agent uses in Claude, Codex, or Gemini: the board, the journal, the map of a repository.
• CLI. npx logishell scan . prints a map of a repository a stranger can read.

What it is not

Not another Claude client. Not a no-code canvas that replaces the terminal. Not a place that stores your provider logins.

The model stays the one you already pay for. LogiShell is the room it works in, and the door it uses.