Share an Agent
Start a ready-made agent or one someone in your community made from its archive, and share an agent you made the same way.
lnk archive export --names agent.coachlnk archive import ~/Downloads/coach.tar.gzlnk agent start --agent coachStart a Ready-Made Agent
Local Link provides four ready-made agents, each ready for one job, with its instructions,
skills, sandbox and any files it starts with. Download one, import it,
keep or change its name, and start it. lnk agent start asks for your
model's credential, as for any agent.
curl -fLO https://github.com/so-local/link-releases/releases/latest/download/link-coder.tar.gzlnk archive import link-coder.tar.gzlnk agent start --agent coderLink's Own Agents
They're released with Link, beside lnk, as
link-coder.tar.gz, link-researcher.tar.gz, link-coach.tar.gz and
link-personal.tar.gz.
Each is an ordinary archive, read by the same checks as any other, and
Link fetches nothing itself. Each is kept in Link's repository, in
agents/, as an archive folder, which the release packs with
lnk archive export --from,
the way you can pack your own, and Link's tests import the same folders
as fixtures, so each works on every release.
How Each Is Kept
An agent's folder holds archive.toml at its top and the agent's
folders as its [map] lays them out: Agents/<name>/, its
instructions, skills and home, and Safe/Agents/<name>/, its
agent.toml and sandbox.toml. Its settings say only what differs from
Link's defaults, each with a comment saying why, and its sandbox file
grants only what its instructions need. Its instructions and skills are
Markdown a model reads: short, concrete and in the second person.
Blank Until You Speak
Each agent's Home starts with only headings, table headers and empty fields, so nothing in it is an example the agent could take for yours. Reference data a skill reads, such as the coach's nutrition values, sits beside that skill instead. Every agent's instructions also say to write exactly what you said, offer anything more as a suggestion, and save a suggestion only once you say yes. A repository check refuses a row, list item, or filled field in any Home.
Packing Them
agents/scripts/pack.sh packs every agent as the release does, into
dist/link-<name>.tar.gz, and imports each into your own ~/Link.
Coding Agent
coder works in one repository, in Rust, Python, TypeScript, Go, Java
and Kotlin, or C and C++, with the toolchains your shell finds, rustup's
and nvm's included. Its sandbox writes only its files folder, the
repository, and runs its toolchains (shell, git, Rust, Node, Python,
Go, Java and Kotlin, and C), each naming its programs, with the programs a build or a
test run writes under them. Its skills explore a codebase, plan a change, write tests,
debug, refactor, fix CI, check dependencies and security, review a diff
and write a commit message, with one for each language's toolchain.
Planning and Language Skills
Its workflow skills apply across languages. Language skills supply the toolchain commands and idioms for the repository it finds. Ask for a plan, review, or audit alone when that is the deliverable, and it inspects the code and produces the requested artifact without implementing or committing.
Its Commits
To commit, its sandbox file grants its repository's .git
(write_dot_files). A hook or git setting it wrote there would run as
you, outside its sandbox, the next time you run git, so review a
change's .git/hooks and .git/config, or take the grant back
(what it opens).
Its Remotes
It fetches, pulls and clones over HTTPS through its proxy, and pushes to
a remote that asks no login. It can't push where a login is asked, as
on GitHub: your git credentials and ~/.ssh stay out of its sandbox, so
it leaves the commit for you to push.
Research Agent
researcher searches the web, reads what it finds and writes a cited
report into its Home. Its sandbox reaches the internet and writes only
its Home. Its skills plan an investigation and check claims against
their sources. It can start from documents you supply in its files folder.
Its sandbox file grants the web tool, which fetches pages once the
web-tool module is on your machine. Search also needs a Brave or Tavily
key: lnk agent tool add web --agent researcher installs both. Missing search does not prevent a report grounded in supplied sources.
Personal Coach
coach keeps your training and food with you in a fixed set of files,
so what it records stays consistent from the first day:
- your profile: goals, the days you can train, limits and equipment;
- endurance sessions, pace and heart-rate zones, races, and a training block such as a marathon's;
- strength sets, an exercise catalogue, records and a program;
- a team's schedule, its practices and games, and position notes;
- the foods you log, with calories and macros per 100 g copied from a reference table beside its food skill, a food log and daily targets;
- body measurements, the week's plan and weekly reviews.
Each log is a CSV file its skills add a row to, which opens in any spreadsheet. Onboarding asks your time zone and creates an evening check-in and a Sunday review and plan after the scheduler's effective zone is confirmed to match it. Saving a profile time zone alone does not configure scheduling. It runs no program and writes only its files folder.
Text Your Coach from a Cloud Box
A coach checks in on its own schedule, so it is most useful where it
never sleeps and where you already are. Kept on a small box in your
Google Cloud account and connected to a Telegram bot of your own, it
answers and checks in while your computer is off. The box costs what
Google charges for an e2-small machine and its disk, and your model
provider bills its calls. Import and start the coach on your computer first.
lnk archive import link-coach.tar.gzlnk agent start --agent coachMake a Small Box and Move It There
The coach runs no program and only reads and writes its files, so the smallest shared-core machine is enough. Make the box first to choose its size, then move the coach to your one box in that account, with its files, conversations, and model credential.
lnk cloud connect gcplnk box create gcp --name gcp-1 --machine.gcp.size e2-smalllnk agent move --cloud gcp --agent coachConnect Telegram on the Box
Make a bot with BotFather, open a shell on the box, and connect the coach where it now runs, as the Telegram guide describes. Pairing happens on the box, so your computer never needs to reach Telegram. Text the bot, and the coach starts onboarding: your goals, the days you train, and your time zone for its check-ins.
lnk box ssh gcp-1Personal Agent
personal learns about you and keeps it in a file for each part of
your life, such as people, work, health and dates, with lists and
notes. It reminds you through schedules and plans your day from them.
Its instructions tell it not to record passwords, card numbers or codes.
Connect it to the
channel you use with lnk agent connect.
Personal Agent Tools
It comes with file, scheduler, memory, web, run, and browser on. Its
sandbox file grants one program, sh, so it runs only a shell's
builtins, and code stays off. Its spec turns its browser on, so its
first start defines one, installing the browser-tool module if it's
missing. The browser needs Chromium, Google Chrome, Microsoft Edge or
Brave on the machine. It has no desktop. A tool this machine can't
serve, such as memory without its engine or web never added here, is
said at start and left out, and the agent starts without it.
Share Your Agent
An agent you made, with the instructions, skills and files you want to
give, goes to your community as one
archive.
Export it, and share ~/Link/Archive/<name>.tar.gz however your
community shares files. Whoever imports it gets their own copy, with an
ID of its own.
What It Carries
An agent's archive carries its whole state, its two folders under
~/Link: its settings and sandbox file from
~/Link/Safe/Agents/<name>/, and its instructions, skills, chats,
memory and Home from ~/Link/Agents/<name>/. Its credentials,
connections' tokens, installed harness and approvals stay behind, since
none of them is under ~/Link, and so do its ID and ports, which are
this machine's records.
Made to Be Shared
An archive holds everything the agent has, its chats and Home included, and export lists what it holds before you send it. Share an agent you made for sharing rather than the one you talk to every day.
Stopped, Here, on Link Harness
Export reads files and nothing else, so it carries an agent only when its
files are all of it. A running agent is refused, naming lnk agent stop,
and so is an agent on a box or a cloud, and an agent on a harness other
than Link Harness, whose own state is in that harness's home: its refusal
names lnk agent harness set link, which brings its
chats and memory to Link Harness so it can be exported. A file in
its settings folder other than agent.toml and sandbox.toml is
refused too.
Import an Agent
lnk archive import <path> checks the whole archive, then tells you the
agent's name and asks whether to rename it. It moves the agent into
place under the name you chose, as a new agent, and tells you the
command that starts it. Nothing is installed, connected or started for
you.
This agent is named coach. Rename it? [y/N] y
Name: my-coach
✓ Imported my-coach.A Name Already Taken
When one of your agents already has the name, import says so and asks
for another, so the clash is settled in the same question and your agent
is never touched. Without a terminal, a name already taken refuses the
import, and --names agent.coach=agent.my-coach names it instead.
What It Opens
An agent's sandbox file comes with it, so it runs with what its author
granted. Import says what that file opens beyond Link's own, such as the
whole network, before you start it, and lnk agent permission remove --agent <name> takes each back.
What an Agent Needs
An agent's requirements are its model provider's credential, its
connections and Link's tools added on each machine, such as its web
tool. Import prints the setup command of each one its files say it's
missing, and lnk agent start names whatever is still missing.
| Requirement | Set up with |
|---|---|
| Model provider's credential | asked for by lnk agent start |
| Connection, such as Telegram | lnk agent connect telegram |
| Link's web, browser or desktop tool | lnk agent tool add web |
A Home Elsewhere
A Home given with --run.files is your folder outside ~/Link/Agents, so it
isn't in the archive. Import says so, and the agent's Home is then its
folder in ~/Link/Agents/<name>/home until lnk agent start --run.files
names another.
Checked as Agents
Import reads each agent's settings and sandbox file with their own
types, and its skills as Link Harness reads them, so a key Link refuses
on a machine it refuses in an archive. Its owner then writes its new ID,
service and ports in ~/.lnk/safe/agents/<name>/, and it's in lnk agent list, stopped, until you start it.