Pages

From 0.20 a site an agent makes, such as a Blueprint plan with its mockups and progress board, opens inside Inyon under Pages. You don't run a server or copy a link around: the agent adds the folder once, and the page is in the app on every device you use.

#How a page gets there

An agent with the Blueprint skill does this on its own when it finishes a site. It runs one command, and you can run the same command for any folder with an index.html in it:

inyon pages add ./private/plans/my-plan --name "My plan"

It answers with where the page sits in the app:

"My plan" is in Inyon: Pages > abhash-arm > custom-tmux
Open it in the app at /pages/local/my-plan

inyon pages lists the pages on a computer and inyon pages rm <slug> takes one off the list. Adding the same folder again is safe and keeps its place. The folder stays where it is, and the app shows its files as they are now, so a page an agent keeps editing is always current. The inyon command has every option.

In the app, Add a folder does the same: pick the machine, type the folder's full path (starting with /, or a drive letter on Windows) and a name.

#On a phone

Pages is the second tab, between Overview and +. Its badge counts pages that changed since you last opened them. The list is grouped by machine, then by project: the folder's git repository, or the repository's main folder when the site sits in a worktree. Each card shows the page's name, a bar with how many tasks are done out of how many, what the agent is on now and when that board was last updated. The bar, the line and the time come from the site's progress.json, so a page without one shows only its name and when it was added. The hub reads it only when it's a plain file of up to 1 MB, not a symlink. A page you haven't opened since it changed has a dot.

Tap a card to open the page full screen. The bar on top has:

• Back, which returns to the list. The phone's own back button does the same, even after you've clicked around inside the page.
• The machine's name, a menu of the other pages on that machine and a way to open the machine.
• ⋯ with Reload, Plan, Mockups and Matrix when the site has them, and Open in browser. Reload opens the page with a new link. Picking a part always loads it, also the one already ticked, which takes you back after the page's own links moved you somewhere else.

Under the bar, a line says Sandboxed page: never sign in here. It stays on screen, so a page can't pass itself off as the app asking for your password.

If the phone loses a hub for a moment (a weak signal, the VPN dropping, the hub restarting), its pages stay on the list, shown as offline, and an open page stays on screen with Can't reach hub now under the bar. Both catch up when the hub answers again. A hub that answers but refuses the phone, because the phone was forgotten there, is different: its pages leave the list and the app says hub forgot this phone until you pair it again.

Long-press a card, or use its ⋯, for Open, Open in browser, Revoke links, Show folder and Remove. Show folder lists the folder's path, the machine, the project and which agent added the page.

The Android app reaches pages through a hub. With only computers paired directly over the phone link, the tab says Pages open through a hub. Tap Pair a hub there, or pair one under Computers, and its pages appear. With several hubs paired, you see all their pages together.

#On a desktop

Pages sits in the sidebar between Machines and Settings, with the number of pages, or of changed pages when there are any. The screen has the list on the left as a tree of machines and projects, with a filter (press / to jump to it), and the open page on the right. Right-click a row for the same menu as on a phone. Clicking the open page's row again opens it with a new link, as Reload does.

Above the page:

A machine's own page lists its pages too, under Pages on this machine.

#Links and removing

The app opens each page with a link the hub signs for that page alone. A link lasts 12 hours. The app makes a new one every time you open a page or press Reload, and again an hour before it runs out, while the page is on screen or as soon as you come back to it. If the hub doesn't answer then, the app tries again after a minute, then waits twice as long each time, up to 10 minutes, while the page stays on screen. The app counts those 12 hours on its own clock from when the hub answered, so a phone whose clock is off still renews in time. Open in browser and Open in new tab make a new link each time, so a tab works for 12 hours from when you opened it. Open the page from the app again for a fresh one.

• Revoke links ends every link made for that page so far: tabs on other devices, links you copied, and the one on screen, which the app replaces at once.
• Remove takes the page off the list, and its links stop working. The folder and its files stay on the machine. The message that confirms it has Undo for a few seconds.

Changing the hub's password ends the links of every page, and forgetting a phone ends the links it made.

#What a page can't do

An agent wrote the page, and an agent can be talked into writing anything, so Inyon treats every page as a stranger's website:

• It can't act as you. The page runs in a sandbox, and the browser treats it as a site of its own. It never sees your sign-in, can't call Inyon to read your sessions or type into them, and can't read anything the app keeps on your device.
• It can't load from the internet. Scripts, styles, fonts, pictures and data have to be files in its own folder, linked with relative paths. A font from Google Fonts or a script from a CDN won't load, so keep them in the folder.
• It can't see its folder's private files. Names starting with a dot, such as .git or .env, are never served, and neither is anything a symlink leads to outside the folder.
• It can't keep things. The browser gives it no cookies and no storage, so a page that tries to save settings gets an error instead.

A page can still run its own scripts, handle its forms in those scripts, open links in a new window and offer files to download, which is what a plan page needs. Security has the details.

#What a page can still do

The sandbox keeps a page away from your sign-in. It can't keep a page off the internet:

• It can reach the internet without you seeing it. No browser lets Inyon block every way out yet. A page's script can open a WebRTC connection, make the browser look up a name in DNS, move to another address or open a window, and nothing on screen has to change.
• What it can carry out is anything the agent that wrote it could read, and anything you type into the page. An agent whose sandbox has no network but can read your disk could copy a key or a token into the page's folder, and the page would send it from your browser.

So treat a page you didn't check like a link from a stranger:

For the same reason, a session's Preview tab won't show Inyon's own address. It says Not shown here, because a preview of the app could act as you. Open agent-made pages under Pages instead.

#When a page won't open