Move Machines

Move your agent to a box in your own cloud, and back, with everything it knows. Its memory, conversations, files, settings and channels come along. Where it can run: Machines.

Move it to a box, and back

Needs a cloud account connected with lnk box. A box costs what your cloud charges for it.

lnk agent move aws                # your only agent, to your box in aws (a new one if you have none)
lnk agent move work gcp-1         # one of several, to your box gcp-1, from wherever it runs
lnk agent move work here          # and back
lnk agent move work aws --image web-ready   # to a new box in aws from your image, set up already

A cloud account's name moves the agent to your one box there. With no box there, move starts one, as lnk box start does, without asking. With several, it lists them: name the box instead. A box this computer didn't make, found in the account by its tags, is asked about first, and without a terminal move says to name it.

Run move on this computer, wherever the agent is. Its memory, conversations, files, settings and channels go with it, and the harness is installed fresh where it lands. Once it answers there, the machine it left deletes its copy and keeps its files in ~/Link/Agents/.moved for 30 days (keep_moved = "90d" or "never" in its ~/.config/lnk/machine.toml changes that). If it doesn't answer, the old machine keeps its copy, stopped.

• --key <key> or the provider's variable (ANTHROPIC_API_KEY and the others above): a hosted model's key, when your agent uses a model on this computer that the box can't reach.
• --image <name>: a new box in that cloud account from your image, even where you have a box, as lnk box start <account> --image makes it.
• work@gcp-1 names an agent when two machines each have one.
• A box with an older lnk is upgraded first.
• Its buckets go with it, so lnk agent backup works there. Without a cloud account that can make a key for them, the move says backups are off there.
• lnk box run <box> -- agent -a <name> <command> acts on it there.
• Whose it is moves with it. An agent made before you signed in moves to any machine; one of your account's only to a machine signed in as your account (lnk auth login there), and a machine signed out or signed in as anyone else refuses it.

Choose where its traffic leaves from

lnk agent exit home       # from this computer's address, over SSH
lnk agent exit direct     # from the box it runs on

On a box, your agent reaches the internet from the box's address. exit home makes sites see your home address instead. This computer then keeps an SSH link to the box open through the vpn plugin and stays awake. With this computer off or offline, your agent on the box has no internet at all; it never falls back to the box's address. lnk vpn list shows whether each exit is up.

The setting belongs to the agent and moves with it. On this computer, traffic leaves from here either way.

Run more than one agent

lnk agent new work                        # Link Harness by default
lnk agent new researcher --harness hermes
lnk agent new helper --on aws-1          # on one of your boxes
lnk agent list                            # every agent, here and on the boxes this computer knows
lnk agent list --refresh                  # and on boxes made on your other computers
lnk agent -a work connect telegram        # -a picks the agent

Each agent has its own settings, files, harness, ports and bot, and the sandbox keeps each out of the others' folders. With one agent, commands act on it; with several, pass -a <name>. The first agent is main. Each agent has its own grants (Choose what your agent can reach); agents on one harness share only what that harness needs.

• A name is lowercase letters, digits and dashes, starting with a letter, at most 30 characters, and not here.
• new takes start's flags. With --on <box>, paste the key when the box asks; --key isn't accepted there.
• list --here skips asking your boxes. A box lists only its own agents.
• list shows the memory each agent here holds and what its model cost over the last day, with the measure plugin (Measure).

Back up your agent

Needs buckets in your clouds (buckets).

lnk agent backup                     # its files, and what its harness knows
lnk agent restore                    # go back to what it knew at the last backup
lnk agent restore -a work --yes      # without asking first

backup stops the agent, then copies its files folder and its harness's memory, conversations and skills to its buckets. Keys are never backed up. restore of an agent that's here replaces what its harness knows with the last backup, for a harness whose memory went wrong. Its files, settings and keys stay. Only the latest backup is kept.

Bring back an agent whose machine is gone

lnk agent restore work                    # finds its bucket in your cloud accounts
lnk agent -a work connect telegram        # its bot, again

For an agent whose box was removed or computer lost. Link finds its bucket in your lnk cloud accounts, asks for the encryption password shown when the bucket was made, and starts the same agent with its files and memory. It asks again for the model key and the channels' tokens, which are never in a bucket.

• --id <id>: which agent, when two agents' buckets have that name.
• start's flags work, such as --key.
• Only its buckets in AWS and Google Cloud are found.

Troubleshooting