agentconnect-cli 0.1.0a1__tar.gz

agentconnect_cli-0.1.0a1/PKG-INFO

@@ -0,0 +1,103 @@
+Metadata-Version: 2.4
+Name: agentconnect-cli
+Version: 0.1.0a1
+Summary: AgentConnect daemon (agentconnectd) and CLI
+License-Expression: Apache-2.0
+Requires-Dist: a2a-sdk[http-server,signing]>=1.2.2
+Requires-Dist: agentconnect-core==0.1.0a1
+Requires-Dist: httpx>=0.28.1
+Requires-Dist: keyring>=25.7.0
+Requires-Dist: mcp>=2.3.0
+Requires-Dist: pyjwt[crypto]>=2.15.1
+Requires-Dist: structlog>=26.1.0
+Requires-Dist: typer>=0.27.3
+Requires-Dist: uvicorn>=0.54.0
+Requires-Dist: websockets>=17.2
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# agentconnect-cli
+
+The AgentConnect daemon (`agentconnectd`) and CLI (`agentconnect`). The
+distribution is `agentconnect-cli`; the command and the import package are
+`agentconnect`. See the repository [README](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/README.md) and
+[SPEC.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/SPEC.md).
+
+```sh
+agentconnect daemon run [--config PATH] [--tcp-port N]   # foreground, JSON logs on stderr
+agentconnect status [--json]                             # reads the local API
+```
+
+Everything protocol-related is in the runtime, `agentconnect.runtime`
+(`Runtime`, with its engine, local API, adapters and agent-scope
+`AgentApi`). `agentconnectd` (`agentconnect.daemon`) is one host of it; the
+Python SDK's embedded mode (`AgentConnect.embedded`, [docs/sdk.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/sdk.md))
+is the other. Both run the same checks, and both serve the local API below.
+
+The invite lifecycle (`group`, `invite`, `accept`, `groups`, `approvals`,
+`verify`, `leave`, `send`, `events`) is documented in
+[docs/cli.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/cli.md), with the `--json` schemas and exit codes.
+`approvals approve`, `approvals reject` and `verify` use the human token:
+**never give an agent the human token or let it run those commands for the
+human.**
+
+Don't give agents shell or file access to the data directory either: an
+agent that can read it can approve joins and mark codes verified as you,
+because the human token is a file there. Agents that need a shell can run
+as another OS user, with the daemon under a user of its own
+([docs/isolation.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/isolation.md)).
+
+## What the daemon holds
+
+- One identity and one instance, created on first start, in the OS keyring
+  when one is usable and otherwise in 0600 key files (`keystore = "auto" |
+  "keyring" | "file"`).
+- The core's MLS state in `mls.sqlite3`, a SQLCipher database encrypted
+  under a `db_key` from the same keystore.
+- Its own `daemon.sqlite3`: groups, members (with the local *verified*
+  flag), Agent Cards, out-of-sync flags, and the durable outbox and inbox.
+  It is a SQLCipher database too, under a key the core derives from
+  `db_key` (ADR-003). Plaintext stays only while it is needed: an outbox
+  row keeps only its ids once the relay has answered it, and an inbox row
+  drops its message once the adapter has accepted it.
+
+The data directory (`~/.local/share/agentconnect`) is 0700 and every file in
+it 0600. Configuration is `~/.config/agentconnect/config.toml`; see
+[docs/config.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/config.md) for the keys and the `AC_*` overrides.
+
+## Local control API
+
+JSON over HTTP/1.1 on a Unix socket in the data directory, or on
+`127.0.0.1:<port>`. Every request needs `Authorization: Bearer <token>`.
+[docs/api.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/api.md) describes the transport, tokens, errors and
+every route with its request and response shapes.
+
+Two tokens live in the data directory: `api-token` (agent scope) and
+`human-token` (human scope, also accepted for everything else). Approving a
+join and marking a member verified are human decisions (SPEC §6.2, §11): an
+agent that could approve its own joins, or mark the short code as compared,
+would remove exactly the checks that catch a leaked link or a relay in the
+middle. Give agent tooling only `api-token`. Both files belong to the same OS
+user, so the split keeps the human capability out of agent integrations by
+default; it is not a sandbox.
+
+Invite secrets never leave the daemon: the URL is returned to the caller and
+the relay only receives the public invite metadata.
+
+## Adapters
+
+`agentconnect.adapter.Adapter` is the interface for agent integrations:
+`deliver(group, sender, to, inner) -> ack | retry`, `on_event(group, event)`,
+`on_outbound(send)` and `capabilities()`. Every delivery carries the SPEC
+§10.1 untrusted framing. A relay frame is acknowledged only after the core
+processed it and the adapter accepted the resulting delivery.
+
+Delivery is **at least once**: after a crash, `deliver` and `on_event` may
+repeat a message or an event. Every delivery has a stable `msg_id` and every
+event a stable `event_id`; deduplicate by them. Nothing is lost: an event is
+recorded before the adapter hears of it and sent again on restart until
+`on_event` returns (ADR-004).
+The webhook adapter ([docs/adapters/webhook.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/adapters/webhook.md)) and the SSE adapter (`GET /v0/events`, [docs/api.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/api.md#event-stream)) serve headless agents.
+`CallbackAdapter` (`agentconnect.callback`) is the embedded SDK's in-process adapter, with the webhook's retry rules. `RecordingAdapter` is the in-memory adapter used by tests. Every message in
+and out goes through the safety policy (`agentconnect.policy`) before any
+adapter sees it ([docs/safety.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/safety.md)).

agentconnect_cli-0.1.0a1/README.md

@@ -0,0 +1,85 @@
+# agentconnect-cli
+
+The AgentConnect daemon (`agentconnectd`) and CLI (`agentconnect`). The
+distribution is `agentconnect-cli`; the command and the import package are
+`agentconnect`. See the repository [README](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/README.md) and
+[SPEC.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/SPEC.md).
+
+```sh
+agentconnect daemon run [--config PATH] [--tcp-port N]   # foreground, JSON logs on stderr
+agentconnect status [--json]                             # reads the local API
+```
+
+Everything protocol-related is in the runtime, `agentconnect.runtime`
+(`Runtime`, with its engine, local API, adapters and agent-scope
+`AgentApi`). `agentconnectd` (`agentconnect.daemon`) is one host of it; the
+Python SDK's embedded mode (`AgentConnect.embedded`, [docs/sdk.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/sdk.md))
+is the other. Both run the same checks, and both serve the local API below.
+
+The invite lifecycle (`group`, `invite`, `accept`, `groups`, `approvals`,
+`verify`, `leave`, `send`, `events`) is documented in
+[docs/cli.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/cli.md), with the `--json` schemas and exit codes.
+`approvals approve`, `approvals reject` and `verify` use the human token:
+**never give an agent the human token or let it run those commands for the
+human.**
+
+Don't give agents shell or file access to the data directory either: an
+agent that can read it can approve joins and mark codes verified as you,
+because the human token is a file there. Agents that need a shell can run
+as another OS user, with the daemon under a user of its own
+([docs/isolation.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/isolation.md)).
+
+## What the daemon holds
+
+- One identity and one instance, created on first start, in the OS keyring
+  when one is usable and otherwise in 0600 key files (`keystore = "auto" |
+  "keyring" | "file"`).
+- The core's MLS state in `mls.sqlite3`, a SQLCipher database encrypted
+  under a `db_key` from the same keystore.
+- Its own `daemon.sqlite3`: groups, members (with the local *verified*
+  flag), Agent Cards, out-of-sync flags, and the durable outbox and inbox.
+  It is a SQLCipher database too, under a key the core derives from
+  `db_key` (ADR-003). Plaintext stays only while it is needed: an outbox
+  row keeps only its ids once the relay has answered it, and an inbox row
+  drops its message once the adapter has accepted it.
+
+The data directory (`~/.local/share/agentconnect`) is 0700 and every file in
+it 0600. Configuration is `~/.config/agentconnect/config.toml`; see
+[docs/config.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/config.md) for the keys and the `AC_*` overrides.
+
+## Local control API
+
+JSON over HTTP/1.1 on a Unix socket in the data directory, or on
+`127.0.0.1:<port>`. Every request needs `Authorization: Bearer <token>`.
+[docs/api.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/api.md) describes the transport, tokens, errors and
+every route with its request and response shapes.
+
+Two tokens live in the data directory: `api-token` (agent scope) and
+`human-token` (human scope, also accepted for everything else). Approving a
+join and marking a member verified are human decisions (SPEC §6.2, §11): an
+agent that could approve its own joins, or mark the short code as compared,
+would remove exactly the checks that catch a leaked link or a relay in the
+middle. Give agent tooling only `api-token`. Both files belong to the same OS
+user, so the split keeps the human capability out of agent integrations by
+default; it is not a sandbox.
+
+Invite secrets never leave the daemon: the URL is returned to the caller and
+the relay only receives the public invite metadata.
+
+## Adapters
+
+`agentconnect.adapter.Adapter` is the interface for agent integrations:
+`deliver(group, sender, to, inner) -> ack | retry`, `on_event(group, event)`,
+`on_outbound(send)` and `capabilities()`. Every delivery carries the SPEC
+§10.1 untrusted framing. A relay frame is acknowledged only after the core
+processed it and the adapter accepted the resulting delivery.
+
+Delivery is **at least once**: after a crash, `deliver` and `on_event` may
+repeat a message or an event. Every delivery has a stable `msg_id` and every
+event a stable `event_id`; deduplicate by them. Nothing is lost: an event is
+recorded before the adapter hears of it and sent again on restart until
+`on_event` returns (ADR-004).
+The webhook adapter ([docs/adapters/webhook.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/adapters/webhook.md)) and the SSE adapter (`GET /v0/events`, [docs/api.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/api.md#event-stream)) serve headless agents.
+`CallbackAdapter` (`agentconnect.callback`) is the embedded SDK's in-process adapter, with the webhook's retry rules. `RecordingAdapter` is the in-memory adapter used by tests. Every message in
+and out goes through the safety policy (`agentconnect.policy`) before any
+adapter sees it ([docs/safety.md](https://github.com/mbocevski/agent-connect/blob/v0.1.0a1/docs/safety.md)).

agentconnect_cli-0.1.0a1/pyproject.toml

@@ -0,0 +1,32 @@
+[project]
+name = "agentconnect-cli"
+version = "0.1.0a1"
+description = "AgentConnect daemon (agentconnectd) and CLI"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.12"
+dependencies = [
+    "a2a-sdk[http-server,signing]>=1.2.2",
+    "agentconnect-core==0.1.0a1",
+    "httpx>=0.28.1",
+    "keyring>=25.7.0",
+    "mcp>=2.3.0",
+    "pyjwt[crypto]>=2.15.1",
+    "structlog>=26.1.0",
+    "typer>=0.27.3",
+    "uvicorn>=0.54.0",
+    "websockets>=17.2",
+]
+
+[project.scripts]
+agentconnect = "agentconnect.cli:app"
+
+[tool.uv.sources.agentconnect-core]
+workspace = true
+
+[tool.uv.build-backend]
+module-name = "agentconnect"
+
+[build-system]
+requires = ["uv_build>=0.13.1,<0.14"]
+build-backend = "uv_build"

agentconnect_cli-0.1.0a1/pyproject.toml.orig

@@ -0,0 +1,33 @@
+[project]
+name = "agentconnect-cli"
+version = "0.1.0a1"
+description = "AgentConnect daemon (agentconnectd) and CLI"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.12"
+dependencies = [
+    "a2a-sdk[http-server,signing]>=1.2.2",
+    "agentconnect-core==0.1.0a1",
+    "httpx>=0.28.1",
+    "keyring>=25.7.0",
+    "mcp>=2.3.0",
+    "pyjwt[crypto]>=2.15.1",
+    "structlog>=26.1.0",
+    "typer>=0.27.3",
+    "uvicorn>=0.54.0",
+    "websockets>=17.2",
+]
+
+[project.scripts]
+agentconnect = "agentconnect.cli:app"
+
+[tool.uv.sources]
+agentconnect-core = { workspace = true }
+
+# The distribution is agentconnect-cli; the import package stays agentconnect.
+[tool.uv.build-backend]
+module-name = "agentconnect"
+
+[build-system]
+requires = ["uv_build>=0.13.1,<0.14"]
+build-backend = "uv_build"

agentconnect_cli-0.1.0a1/src/agentconnect/__init__.py

@@ -0,0 +1,3 @@
+"""AgentConnect daemon and CLI."""
+
+__version__ = "0.1.0a1"

agentconnect_cli-0.1.0a1/src/agentconnect/a2a_adapter/__init__.py

@@ -0,0 +1,6 @@
+"""The A2A adapter (docs/adapters/a2a.md): A2A v1.0 server agents in groups,
+and an A2A server facade on loopback for local A2A clients."""
+
+from agentconnect.a2a_adapter.adapter import A2AAdapter, A2AOptions
+
+__all__ = ["A2AAdapter", "A2AOptions"]