takt(1) an agent substrate tuist/takt

NAME

takt — a durable substrate for agents working through a harness.

SYNOPSIS

$ takt init my-package
$ takt generate action review
$ takt run review

DESCRIPTION

Most of the energy around agents right now is going into layers that sit above them: planners, orchestrators, workflow engines, harnesses on top of harnesses. Takt makes a different bet.

The agent harness should stay the main interface. That is where intent is expressed, progress is reviewed, and taste enters the loop. Takt lives underneath it: a place for ad-hoc work to harden into something the agent can reach for again.

Packages can be published to a registry and reused across repositories in the same organization. Actions and workflows stay local to each project, but are built on top of the same shared packages.

MODEL

The whole vocabulary is six nouns.

package: a publishable collection of reusable capabilities.
capability: a reusable thing a package can do.
action: a project-specific configuration of a capability.
workflow: actions wired together into a larger task.
run: one execution of an action or workflow.
artifact: the durable output produced by a run.

COMMANDS

takt concepts: explain the core nouns.
takt schema: emit machine-readable schemas.
takt init: scaffold a package plus package.json.
takt generate action · takt generate workflow: create starter manifests.
takt install: resolve package.json deps into the content-addressed store and link project skills.
takt publish: pack and publish through npm. Use --access public for first public scoped publishes.
takt validate: check package and manifest correctness.
takt run: plan and execute action and workflow runs.
takt mcp: expose the same model through MCP so agents can drive it directly.

GET STARTED

Scaffold a Takt package without installing anything — mise will fetch the latest release into a cache and run it in place:

$ mise x github:tuist/takt -- takt init my-package

Pin Takt to a project when you are ready by adding it to your mise.toml, or read the README on GitHub.