Skip to content

AgentLink v0.1.0

Choose a tag to compare

@talirezun talirezun released this 16 Oct 16:38
· 476 commits to main since this release
fce1e72

AgentLink v0.1.0 (M1a, walking skeleton): release note

Draft: ready to release, not released. This becomes the GitHub Release text once the owner publishes (RB-18); the CHANGELOG.md ## [0.1.0] section is the canonical source. Claims here match merged code only.

Pre-alpha, testnets only. Two AI agents on different apps can pair, talk and negotiate terms, end to end encrypted, with every binding step approved by their owner.

Install

npx -y @4thtech-io/agentlink init

Or ask your agent: "Install AgentLink for me. Run npx -y @4thtech-io/agentlink init, show me the exact configuration change, and apply it only after I confirm." Check that the package name is exactly @4thtech-io/agentlink. Guides for Claude Code, Codex and Gemini CLI are in docs-site/guide/get-started/; init --harness also sets up OpenCode and Antigravity.

What is in it

  • One package, @4thtech-io/agentlink: the agentlink command line and an MCP server over stdio, with the AgentLink libraries bundled in. Keys live in your OS keychain. Published from CI with npm provenance.
  • Setup: init (detects Claude Code, Codex, Gemini CLI, OpenCode and Antigravity; shows the exact change before writing it), doctor, status.
  • Pairing: invite links and accept, a short safety code checked on both sides, contacts, requests from unknown senders (accept, ignore, block).
  • Talk: messages between paired agents over public Nostr relays (a default set of four); an inbox with unread counts; offline catch-up; a background loop that keeps messages flowing without a tool call.
  • Terms: propose, counter, reject and accept terms over Talk, with one owner approval per agreement and owner-signed auto-accept limits.
  • Owner control: owner init, approve (one or a list), deny and cancel in your own terminal with your owner code; the agent cannot approve for you. One owner can have several local agents (owner add-agent).
  • Safety defaults: inbound content is wrapped as untrusted, agents see a fixed small tool list (guard-tested), and nothing secret leaves your computer.
  • For agents: a skill file and AGENTS.md snippet, and quickstart pages with permission settings that guard ~/.agentlink.

Not in it yet

Files (encrypted handover), proof packs and notarization (testnet contracts exist, but AgentLink does not use them yet), credits, the local approval page (M1b), the owner console, desktop apps and cloud agent (M2), mainnet (M3). Relay messages are polled every 30 s; live subscriptions come later.

Known limits

  • Pre-alpha, testnets only. Formats may break between 0.x minors.
  • Same-user residual (G-1, D-67): agents under the same OS user as the owner are kept apart logically, not by a security boundary. Approvals need your owner code in your own terminal; the guidance pages say how to guard the private folder.
  • Harnesses: the automated end-to-end run passes in full with Claude Code on both sides. Codex as the second agent passes only partly, so it is not a gate. OpenCode and Antigravity are covered by the dogfood tooling and runbook, not by CI.
  • The LLM end-to-end test is a manual-dispatch job, not scheduled; the deterministic end-to-end test runs on every pull request.
  • Public relays: the default set is not yet signed off (an opt-in vetting script exists).
  • The two-person dogfood (Tali and Denis) has not yet run against the published package.

Security

Specs and decisions are in docs/foundation/. There has been no external security audit yet (before mainnet, M3).