Plexon Nous
on a Machine of Your Own

Plexon Nous is the part of Plexon that runs your workflows, bots and boards, kept on a machine that does not get closed at night. On the Nous box it is already on. On a spare computer with Plexon installed, one switch does it: Settings, This computer, "Let my other computers connect to this one". It then shows a six-digit code for the other computer to type. Reaching that computer from another network is a second switch under the code, "Reach this computer from the internet", on by default and yours to turn off: while it is signed in it gets a name under nous.plexon.ai, reached through Plexon's relay, shown once Plexon has checked that the computer answers through it (a signed-out one still pairs but gets no name). The computer keeps its own connection out to the relay, so there is nothing to set up at home, and a phone hotspot or a provider's box in front of your line makes no difference. The connection stays encrypted end to end with that computer's own certificate; the relay passes it along without opening it. Away from home the app uses that computer as it does at home: attach files and pictures, dictate, use its Browser panel and sign connectors in for it, with a big send taking longer through the relay. A box with no screen is one command: on Windows 11 or a Linux with systemd, the setup line on the download page installs the current release, starts it as a service that returns after a reboot with nobody signed in, and prints the address, token and fingerprint the app asks for. Once paired it gets its name under nous.plexon.ai like any other computer of yours. The app lists it under Your Nous boxes with its address on your network and that name, and away from home it reaches the box through the name. Reach this computer from the internet is switched for that box from the app. Off keeps it on its own network, and since only a computer on that network can turn it back on, the app asks first. A box you are connected to also updates from the app. Under Settings, This computer, Show all options, its Updates block says when a newer release is out, and Update from the internet installs it; the box checks GitHub once a day, and it can install on its own at a quiet moment when you switch that on. The same block can push a build from your computer instead. Either way the box is back in about a minute or two. Its log shows in the app too: Plexon's log under the box's row lists the last lines it wrote, with a filter, and Follow adds new ones as they come.

• Already on, on the Nous box
• One switch on a spare computer; one command on a Windows 11 or Linux box with no screen
• Comes back after a reboot with nobody logged in
• Updates from the app, with a build on your computer or the latest release

Settings, This computer, Plexon Nous lists the computers on your account that are ready, with when each was last seen and whether it can be reached from here. Pick one, type the six-digit code it shows, and the app connects and restarts onto it. The code is good for five minutes and one use; three wrong tries cancel it. Across a network the connection is encrypted with that machine's own certificate, and the key the app keeps for it lives in the operating system's keystore. A machine set up from the command line is added with Enter by hand instead. When the app runs on one of the listed computers, its row is marked This computer.

• Your computers listed by name, a six-digit code to pair
• Pinned to that machine's own certificate, never a certificate authority
• Nothing to type for a computer on your account; Enter by hand for one set up by hand
• Switch to the local computer brings the app back

On the computer that stays on, Paired apps sits under the pairing code. It lists every app that has paired with that computer, by the name it got when it paired. An app connected right now shows its address and since when; the others show when they were last seen. Remove takes one off: it disconnects within seconds and has to pair again with a new code.

• Every paired app by name, connected now or last seen
• Remove one and it disconnects within seconds

Everything that runs on a timer or answers a message keeps going on Plexon Nous: schedules, Gmail and WhatsApp reply handling, Telegram and Slack bots, dashboard refresh. Open the app on the laptop later and the runs are there.

• Schedules and polls fire on Plexon Nous
• Reply workflows answer Gmail and WhatsApp there
• Telegram and Slack bots answer from there
• Boards refresh on their timers and show fresh numbers when you open them

A computer you leave running has a browser of its own, the way Plexon Nous Cloud does. Browser workflows run there, on that computer, and not on whichever laptop happens to be connected at the time. While the laptop is connected, its Browser panel draws that computer's browser live: you click, type and sign in from the laptop, and the sign-in stays on the machine doing the work. Sit down at that computer later and you are still signed in, in the same browser its own panel shows. Sign-ins you already have on the laptop are copied over when it connects, and they fill gaps only: a site that computer is signed in to keeps its own session, and signing out on the laptop does not sign it out there. One thing it does not get is Browser address, the proxy that hands the sites a workflow visits a different address. A computer of your own browses from its own address, and that browser is one a person sits in front of, so Plexon puts no proxy under it; Browser address stays with Nous Cloud. A box set up with the one-command installer has a browser too, with nobody signed in: the installer keeps the whole app and the box runs it as its browser, so browser workflows run there with no laptop connected. On a computer of yours with the app closed there is no browser, and a browser step falls back to a connected laptop's hidden window, as before.

• Browser workflows run on that computer, with the laptop closed
• A box set up with one command runs its own browser too
• One browser, watched and signed in to from either side
• Sign-ins copied from the laptop fill gaps, never replace

When you connect, the app asks the signed-in Plexon on your laptop for a device grant and hands it to Plexon Nous. It then signs in on your account's device seat, not yours: switching back does not sign it out and it does not sign you out. It appears under Devices on your account page, where Revoke signs it out.

• One grant per machine, listed under Devices
• Revoke from the account page; its automations stop until it is paired again
• Your own sign-in is untouched

The app talks to one Plexon at a time, this computer's or Plexon Nous. While it is pointed at Plexon Nous, the workspace is that machine's folder. A file you attach is uploaded there and the model reads it there; images and documents the app shows are read from that machine; a connector sign-in still opens in your laptop's browser and completes on Plexon Nous.

• Attachments upload to the Nous workspace
• Open and Reveal say where the file is instead of failing
• Connector sign-ins finish through your own browser

While the app is connected to it, every folder is that machine's. Browse shows its disk, New folder makes one, New workspace finishes on it, and Send a folder copies a folder from your computer to it, up to 1 GB a send.

• Browse, New folder and New workspace work on its disk
• Send a folder: node_modules and build output stay behind unless you keep them

Moving a workflow you built on the laptop to Plexon Nous, with everything it depends on, is planned as an export and import; no date is promised. If you have no machine to leave on, Plexon Nous Cloud is the same thing run by Plexon, turned on from the same Settings tab, and part of Premium.

• No moving a workflow between the two yet; build it where the app is connected
• No machine to leave on: Plexon Nous Cloud, part of Premium