Stores keep every chat where you choose
Everything your agent keeps is kept at a place: its folder on this machine, a SQLite file, or its own encrypted bucket. A store driver keeps each place, outside the agent's sandbox, and the agent and its tools reach every one through the same storage bridge.
The places
An agent's things are six collections: its Home, instructions, skills, memory, conversations and schedule (Agent Spec). Each is kept at one of Link's places, by that place's driver, outside the agent's sandbox.
file
lnk-file-store keeps every collection as ordinary files in the
agent's folder on this machine, LNK_STORE_DIR, which you read and
edit as they are. A conversation's events are appended to a log, with a
readable copy beside it, and the driver follows no link within the
agent's folder (File Store).
sqlite
lnk-sqlite keeps all but home as rows of one SQLite file in the
agent's folder, which moves with the agent's files (SQLite
Store).
bucket
lnk-bucket-store keeps every collection as objects in the agent's
bucket, the first encrypted one lnk bucket connected for it, safe on
one machine at a time (Bucket
Store).
Off the machine
lnk-gcs keeps an agent's conversations off the machine instead, in a
Google Cloud Storage bucket, so any machine reading the bucket can take
the agent's next turn (Google Cloud Storage
Store).
Choose where they're kept
An agent's spec says the place it prefers for each collection, in its
[storage], and its machine decides: a machine's machine.toml lists
the places it supports, and the agent's preference holds where the
machine lists it (Where an agent's things are
kept).
A place whose driver isn't installed is installed as a plugin.
Link Harness
shows a conversation kept in SQLite or in Google Cloud Storage.
Write a driver
A driver is a program, lnk-<name>, that answers contract, call
and serve, which the storage bridge invokes outside the agent's
sandbox: its Interface.