1. Chat that edits, with a stop
Ask in ordinary language. It reads, proposes a patch, and waits. One yes is not a blank cheque for every later shell.
One PC is enough. A company that already bought a room of desktops can put them on the same private fleet overnight. Nothing in the prompt has to leave the site. The installer lives on Downloads.
Local or cloud model. No tools until you open them.
Point it at a folder. It can read. Writes wait for your yes. That is the difference between a chatbot and a worker.
The installer will join a Core already on the LAN. Enrol PulSen Craft. Now a chat can become a job the rest of the machines can see.
Most people type and hope. PulSen Craft is that same chat — with tools, approval, and a terminal in the thread.
Ask in ordinary language. It reads, proposes a patch, and waits. One yes is not a blank cheque for every later shell.
The integrated terminal is in the turn, not a side hobby. You see the command, the output, and the next sentence in one place.
If Core is connected, a chat can become a governed job: cheaper seat, live status, evidence. That is the jump from “AI chat” to doing work.
Live capture from the Core, shown here as a demo. The bits to install it are on Downloads, not this page.
Home lab, workshop, or a company that already owns the PCs. The self-serve beta is on Downloads. Photos, invoices, and overnight monitoring are on Systems.