Troubleshooting
What to do when your agent's browser doesn't start, reach a page or keep a sign-in (Link Browser).
"no Chromium here"
The tool found no browser it drives. Install Chromium or Google Chrome,
or name its program with --chromium <program>.
"the browser didn't start"
The answer ends with the browser's last words. Chromium from a snap can't run in the sandbox: install it from your distribution or Google.
A Chrome crash dialog on macOS
Update the browser plugin as well as the agent and harness, then run
lnk agent restart and retry. The browser needs read access to its
selected .app bundle to load frameworks and helpers. That access is
included in its own sandbox and does not open other applications or your
personal profile. A startup failure reports the browser's last words and
that no page was opened.
Find the denied resource
After a failed attempt, run lnk agent logs. Tool failures include the
tool name, chat and error. If Chrome's dialog remains, its report's
Termination Reason and framework path help identify the denial. Share
those diagnostics without tokens or passwords. The browser's resource
permissions belong to its plugin, so granting the agent your whole home
is unnecessary.
"on this machine or its network"
The page is local, on this computer or your network, which the browser
never reaches. --private-host names a host you trust.
"there's no [3] on the page now"
A part's number is that of the last read, and the page changed since: read it again for its numbers.
A site doesn't remember the sign-in
Each agent has its own profile, which keeps its cookies; give the same
--profile.