Troubleshooting
What to do when switching harnesses goes wrong, one symptom to a heading.
use says there's no harness by that name
Add it first, from Link or from its own repository, then switch to it by its name: Use another harness.
" doesn't speak Slack"
Run lnk upgrade, in case the harness's plugin is older than the
connection, or lnk agent use the harness the message names.
start says the harness asks for more than Link's defaults
Run it in a terminal to answer its question, or add --yes to agree
ahead in a script.
A harness's need you said no to
Run lnk agent harness allow with the flags its start shows, such as
--network-mode host, or a risk's name; or run lnk agent harness reset --harness <name> to be asked again on its next start.