Start here

One ledger. Two actors. Five minutes.

Install Tasq Local, create one explicit workspace, then hand any shell-capable agent the versioned onboarding response.

Try it without installing

Run one complete task cycle in three seconds: it creates a task, lists it and completes it. Either supported package runner works. This installs nothing permanently and does not read or write any ledger you already have.

try without installing

npx @tasq-run/cli@0.6.2 demo
bunx @tasq-run/cli@0.6.2 demo

Install the public alpha

Tasq Local 0.6.2 is a public alpha. The versioned installer selects only a certified platform asset, verifies the pinned checksum manifest and installs side by side without editing your shell files.

verified persistent install

curl -fsSLo /tmp/tasq-install.sh https://tasq.run/install-v0.6.2.sh
sh /tmp/tasq-install.sh --dry-run --version 0.6.2 --prefix "$HOME/.local"
sh /tmp/tasq-install.sh --version 0.6.2 --prefix "$HOME/.local"
"$HOME/.local/bin/tasq" version

Inspect the downloaded script before running it. Uninstall removes only managed program files; TASQ_HOME, the ledger and backups remain untouched. The npm-prefix path remains available in /adopt.json for machine acquisition.

Give an agent the minimum causal pointer

An agent cannot discover a local executable or shared database by intuition. Give it the executable path, workspace, stable actor label, capability envelope and current intent.

The response uses the real tasq.autonomous-bootstrap.v1 contract. Read guide.firstReadRecipeId, then execute only the returned argument-array recipes.

agent bootstrap

TASQ="$HOME/.local/share/tasq/node_modules/.bin/tasq"
"$TASQ" onboard \
  --space robotics/team-a \
  --actor agent:planner \
  --capabilities read,propose,coordinate \
  --json

Keep everyone on the same authority

The same workspace name on two isolated stores does not create collaboration. Local actors rendezvous only when they use the same TASQ_HOME and exact workspace.

Persist returned commitment IDs, revisions and event cursors.
Read before mutating and use idempotency keys for retryable writes.
Treat actor labels as attribution, not login or permission.