Outsider Stage 0.5
Replay and verify a real, sealed Outsider Stage 0.5 intervention chain.
Translation pending
Opt-in, local-first, end-to-end encrypted sync for ak secrets across trusted devices. Protocol v1 reviewed by the owner, not independently; sync is pre-release.
SecurityTypeScript · GoGitHub @bestagentkitsOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Credentials vault for AgentKit
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Opt-in, local-first, end-to-end encrypted sync for AgentKit secrets (ak secrets)
between your trusted devices. The server stores ciphertext and a small, documented
set of operational metadata; it never holds a key that can decrypt your secrets.
Landing page: https://vault.agentkit.best
The current state of every surface (local vault, sync, dashboard, remote MCP) and its gate is on one page: docs/status.md.
ak secrets sync commands can sync to it. It is not independently reviewed and not
yet recommended for production credentials. Open items are in the
release gates.AgentKit's local vault works without this service and without a network connection. Sync is off unless you turn it on.
Remote access (pre-release; on in production by owner decision, before its release gate): a
browser dashboard at /app, where the browser is an enrolled device, and a remote
MCP endpoint at /mcp for hosted AI tools. During a remote MCP call plaintext passes
through Worker memory; it is never stored or logged
(ADR 0002 D7). User steps
are in the guide, operations in the
runbooks.
AgentKit vault v1 keeps secrets on one machine. Using them on a second device, and later in shared or CI vaults, needs sync that does not trust the server with the secrets, does not lose concurrent edits, and does not let a stale device bring back a deleted credential. The reasoning and the limits are in the ADR and the threat model.
| Path | Contents |
|---|---|
docs/protocol/v1/spec.md | Normative protocol v1 wire spec |
protocol/v1/vectors/ | Deterministic test vectors shared by every implementation |
packages/protocol/ | TypeScript reference implementation |
go/ | Go implementation |
worker/ | Cloudflare Worker and per-vault SQLite Durable Object; worker/public/ is the landing page |
docs/ | Design, security and operations docs (index) |
The AgentKit CLI and Desktop client live in bestagentkits/agentkit; account login and vault tokens in bestagentkits/ak-web.
Requires Node 22+, pnpm (version pinned in package.json) and Go.
pnpm install
pnpm typecheck
pnpm test
pnpm build
cd go && go test ./...
Read AGENTS.md before starting: it covers the issue and label workflow, security rules, and what a spec change requires. Reviews follow REVIEW.md.
Do not post exploit details or secrets in public issues. Report vulnerabilities privately through GitHub's private vulnerability reporting.