Tools and Skills
Choose the tools your agent can call, and add reusable instructions for recurring work.
lnk agent tool listGive It Tools
Add Local Link's tools to your agent, or take them away, one at a time.
lnk agent tool add weblnk agent tool remove webState is on when the tool is configured for this agent, and off
otherwise. An installed module alone does not enable its tool. File starts
on, so when you ask, your agent changes its files, instructions, and skills.
Scheduler, run, and code start off in every profile.
Set Switches and Grants
add and remove save
the tool's [behavior.tool.<name>] enabled switch in ~/Link/Safe/Agents/<agent>/agent.toml, preserving
other opinions and comments. You can also set that switch yourself.
Grant the folders or programs each tool needs in its sandbox file.
Only confirming a proposal widens those grants. The tool refuses a request outside them.
Saved memory uses its separate notes permission.
Choose a Capability
Choose the capability you need. Each adds an independent tool to the same agent, and installing every tool is optional.
lnk agent tool add link|memory|browser|desktop|file|schedulerRun Local Link Commands
The Link tool starts enabled. The tool reads documentation, inspects capabilities, and offers explicitly declared commands. Read calls are allowed, while changes ask through the sandbox. Remove the tool with lnk agent tool remove link and add it again with lnk agent tool add link.
Approve Missing Sandbox Permissions
Adding a built-in tool displays any missing file or program permissions
and asks before saving them in ~/Link/Safe/Agents/<agent>/sandbox.toml. Without approval,
the tool stays off. --yes explicitly approves the displayed proposal.
Existing sufficient grants are reused. Removing a tool switches it off
without revoking grants that another tool may share. Setup and tool
switches live together in ~/Link/Safe/Agents/<agent>/agent.toml under [behavior].
Add Web
add web installs Link Web if it isn't here, and takes its search key
from BRAVE_API_KEY or TAVILY_API_KEY, else asks for it. Without
a key, your agent fetches pages but doesn't search. The key stays with
Local Link's sandbox, outside your agent. lnk sandbox tool list shows Web's shared
definition, and lnk sandbox tool remove web removes it for every agent.
Add Web on a New Machine
An agent's sandbox file can name web on a machine where it was never
added, such as one you imported the agent to. The agent then starts
without web and says so, with lnk agent tool add web --agent <agent>
as the step that adds web here. A tool of your own that was removed
since says instead how to forget it.
Add a Tool of Your Own
Add a tool of your own, an MCP server
lnk sandbox tool add defines, by its name. Each change says
where it's written. Local Link's tools has each one.
Restart for a Change
A running agent gets a change when it restarts, and each change asks
before restarting the agent. lnk agent tool add --yes restarts the agent without
asking. With no terminal to ask in, the agent keeps running as it was, and
lnk agent restart gives it the change.
Inspect Available Actions
In Link Harness, /tool:list reports the namespaces and action names
exposed to the current agent. The command reads capability metadata without
enabling a provider or granting a tool. Command rules
explain owner-only slash invocation and unavailable commands.
Add Reusable Skills
Add task instructions your agent can read and reuse with Skills. Skills are ordinary files you can inspect and edit, and installing one grants no extra permissions.
Understand Tool Boundaries
What the memory, network, browser, program, and file tools reach is in Security. Scheduled work, bounded delegation, and retained delivery are in Decisions.