tkhq/tk has 64 GitHub stars and 3 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 22:35 UTC. Last push 2026-11-06.
Measured star growth
- in 24h
- 0
- in 7 days
- Update delayed
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Git signing and SSH for agents, with expressive policies and keys that never leave Turnkey.
Developer ToolsREADME.md
Original
Git signing and SSH for agents, with keys that never leave Turnkey.
tk lets an agent sign Git commits and open SSH connections without a private
key on its machine. Turnkey holds the key, enforces expressive policies on
every signature, and logs every approval.
- Git signing:
tkacts as Git's SSH or GPG signing program, sogit commit -Sandgit verify-commitwork unchanged. - SSH:
tk ssh agentserves Turnkey keys on a standardSSH_AUTH_SOCK, sossh,git push, andgit cloneover SSH work unchanged.
Local agents
For an agent on your laptop, for example Claude Code or Codex in a terminal:
- No key for the agent to read: the signing and SSH keys stay in Turnkey,
not in
~/.sshor a GnuPG keyring that the agent could read or copy. - Its own identity: the agent signs and connects with its own key, not yours, so its commits are attributable and its access can be revoked without touching your keys.
- Policy and audit: expressive Turnkey policies decide which keys the agent may use, and Turnkey logs every signature and approval.
Background agents
For an unattended agent in CI, a container, or a VM, the agent never holds a long-lived credential:
- Expiring session keys: the agent generates its own API key, and a separate provisioner registers it with an expiry and renews it.
- Signing broker: a separate process holds the signing credential. The agent gets only a Unix socket and a public key.
- Policy-scoped signing: each agent can sign only with the keys a policy names. Revoking its API key cuts it off at once.
Getting started
Paste this into your agent:
Install the Turnkey tk CLI with
`curl --proto '=https' --tlsv1.2 -LsSf https://raw.githubusercontent.com/tkhq/tk/main/install.sh | sh`.
Install the tk skills with `tk skills install --into <your skills directory>`,
read the installed turnkey-tk/SKILL.md, and walk me through bootstrapping my
Turnkey organization at https://app.turnkey.com.
Manual installation
curl --proto '=https' --tlsv1.2 -LsSf https://raw.githubusercontent.com/tkhq/tk/main/install.sh | sh
We recommend installing Cosign 2.4.2 or later first so the installer verifies release signatures.
To verify a release archive and its matching .sigstore.json bundle downloaded
from Releases manually:
cosign verify-blob-attestation tk-aarch64-apple-darwin-vX.Y.Z.tar.gz \
--bundle tk-aarch64-apple-darwin-vX.Y.Z.tar.gz.sigstore.json \
--type slsaprovenance1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/tkhq/tk/.github/workflows/release.yml@refs/tags/vX.Y.Z
Docs
Git signing and SSH:
- Git signing: sign commits and tags with SSH or GPG keys held in Turnkey
- SSH: registered keys and the SSH agent
- GPG signing: OpenPGP keys, the GPG agent, and GitHub setup
Running background agents:
- Sessions: expiring keys registered by a provisioner
- Secrets: inject credentials into an agent at startup
Foundations:
- Authentication: profiles and the environment bundle
- Resources: users, policies, API keys, and wallets
- Activities: inspect, approve, reject, and wait
- Signing: payloads and serialized transactions
- Raw requests: sign and send an exact request body
- Skills: the agent skills package embedded in the binary
- Command reference: every command and flag, generated from the parser
Contact us
tk is part of Turnkey's agent auth beta. To ask a question or tell us what
your agents need, reach us at
turnkey.com/agent-auth-beta.
For the thinking behind this project, see this thread.