Where the agent actually executes
Tulsk provisions a workspace computer in its own container per workspace. You don't install anything, you don't decide the runtime — Tulsk handles it.
Every Tulsk agent executes through the same managed workspace-computer runtime.
Multica installs a Go daemon on your machine via Homebrew or curl. The daemon scans your PATH and auto-detects which agent CLIs you already have, then routes assigned issues to whichever one matches.
Great if you want one dashboard over the agent CLIs you already trust. You manage the daemon process yourself.