tasq

Start here

One ledger. Two actors. Start from source.

Clone and build Tasq Local from the public canonical source, create a workspace, then hand any shell-capable agent a bounded onboarding response.

Current installation path

Tasq is public alpha source. There is no published npm package or downloadable release yet, so clone the canonical repository and use the deterministic source-build path below.

example
git clone https://github.com/gwendall/tasq.git
cd tasq
pnpm install --frozen-lockfile
pnpm typecheck && pnpm test
pnpm build:cli
./dist/cli/index.js version

Do not install the unrelated unscoped npm package named tasq. Future packages use the @tasq scope; the executable remains tasq. Machine consumers can fetch /adopt.json for the same public source-build path as argv arrays.

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 onboarding response is versioned JSON. It describes supported capabilities and returns argument-array recipes, so the agent does not need repository-specific instructions.

example
./dist/cli/index.js 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.