Create Another Agent
Create an additional agent with its own name, model, files and connections.
lnk agent create workRun More Than One Agent
Run as many agents as you like, each with its own settings, files, harness, ports and bot.
lnk agent create worklnk agent create scout --harness hermeslnk agent create writer --on aws-1lnk agent listlnk agent list --refreshlnk agent connect telegram --agent worklnk agent list asks your boxes for their agents too. --refresh also
asks your clouds for boxes made on your other computers, and --here
lists only this machine's agents, asking nothing else.
lnk agent list --hereKept Apart
The sandbox keeps each agent out of the others' folders. With one agent,
commands act on it, and with several you pass --agent <name>. The first
agent is main. Each agent has its own grants
(Choose what your agent can reach),
and agents on one harness share only what that harness needs.
Create on a Hosting Account
lnk agent create work --on <account> makes a blank agent directly on
an account that hosts agents, using its harness and model defaults. It
asks for no model provider credential and makes no local copy. The account bills the
agent it runs, so create asks first. --yes answers yes, and with no
terminal and no --yes it makes nothing. lnk agent list shows
it there; lnk agent connect telegram --agent work connects it through
that account. A box name after --on still creates the agent on the box.
Create With an Environment
lnk agent create work --env env.toml sets an environment
up on this machine for the new agent, as lnk env setup here does. No
VM is made for it. Its stages run each in its sandbox, or directly while
the agent runs with --no-sandbox. Its services start with the agent and
stop with it. The environment is captured once, at creation, and kept in
~/.lnk/safe/agents/environments/<name>.json. An existing agent keeps
the environment it was created with.
Create Inside a VM
An agent here runs in a VM (virtual machine) only where a VM provider is
installed and this machine's owner requires one (vm_required), as
VM Boxes
describe. lnk agent create work --env env.toml then creates a private
guest through the box machine interface, from the host's approved
profile, and prepares the environment in the guest. An existing native
agent keeps its authority until explicitly moved.
Captured Inputs
The agent's own spec may name env, relative to that file. A spec never names a sandbox file or no sandbox, which are each start's own, and its [isolation] table's vm is refused.
Command-line paths are relative to the caller. Creation captures their
content once. Later edits affect future creation, rather than modifying
the running agent's VM, environment or approved network grant.
Runtime Placement
The complete runtime, harness installation, hooks, native tools and
children run in the guest. The controller records the guest identity
before activation and forwards later start, use and other agent commands
to that exact identity. A later start's --spec file, with its field
flags over it, is copied into the guest as the effective spec, as its
creation's is; field flags alone go to the guest, over the agent's own
spec there. Stop/start restores the retained guest and its
captured environment. A removed or replaced guest causes a refusal;
there is no native placement fallback.
Created and Borrowed Guests
Creating on an existing VM box borrows it and retains that box's captured inputs. Removing the agent preserves a borrowed box. Removing an agent whose creation owns its guest removes that guest only after the agent's removal succeeds. Interrupted creation retains its identity for retry or explicit removal, without running setup on the personal host.
Approved Programs and Connections
The approved Linux base needs verified Link and sandbox artifacts. An explicit guest service supervisor supports bases without systemd. If outside traffic is needed, the owner approves a filtering bridge in the guest's bootstrap profile. Guest credentials are configured explicitly; the controller's model provider credentials and SSH agent are not forwarded. Existing dedicated cloud VM boxes keep their networking and do not create a nested guest automatically.