Tutorial

Reference tells you what exists. This section tells you what to do with it.

Two kinds of pages live here, and both are written after the thing actually ships, not before:

1. A feature page answers "we built X, how do I use it?" It names where to click, what you should see, and what it looks like when it goes wrong.
2. A recipe runs end to end across several features: connect a machine, put an agent on it, show someone the result.

Every page is a link you can send. If a step below does not match what you see in the app, the page is wrong and we want to know: the feedback tool inside the product goes to the same people who write these.

Where to start

New here? Install and the first hour comes before anything on this page. Then connect a machine, because almost everything else in LogiShell happens on hardware you own.

Pages

• Connect a machine: One command turns any computer with internet into LogiShell compute. Nothing has to be open to the internet on its side.
• Run an agent in a terminal: A real shell on a machine you own, in a browser tab. Closing the tab does not kill the agent, and the conversation continues instead of starting over.
• Prove that it works: A run answers "does it work". A proof answers "where can I look", survives the next run, and attaches to a card.
• Share a page by link: A document in LogiShell is a file on your machine. Publishing it gives that page a link you can send, without moving the file anywhere.
• Install LOG on a Wear OS watch: Two bundles, one adb session. LOG on the wrist approves runs and watches your machines; the watch face is its own install.
• Add LOG to your product: Connect a website, install LOG with React, Next.js or JavaScript, and collect private feedback with screenshots and video.