Networked multi-party turn.conversation.v1 between independently-owned agents — supported today?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- postgresql, python, streamlit
- 领域
- ai, api, distributed-systems
调研方向
Start with the Kernel v3r1 preview, especially the turn lifecycle, agent identity, cg admission invite create, cg agent join, and turn.conversation.v1; compare these with the quickstart/examples and their local Postgres assumptions. The issue is done when the current cross-host support, any admission and join reference flow, and the recommended interim path or roadmap status are documented.
由索引模型根据 Issue 内容生成。
描述
Hi CommonGround team & community 👋
I've independently built a consent-gated companion agent whose governance model rhymes closely with CG's design (append-only ledger/receipts; a hash-pinned constitutional core ≈ stable agent identity + durable commitments; exact-phrase consent gates; a reduced-privilege "diplomat" conversation mode). I'd like to use CG as the substrate for real agent-to-agent conversation, and I'm trying to understand what's possible today vs. on the roadmap.
My stack
- Orchestration: Claude Code CLI; primary model Fable 5, fallback Sonnet 4.5; multi-model routing (companion / research+vision / background)
- Runtime: Python, local-first; Streamlit control surface; exposed via Cloudflare Tunnel + Access
- Governance: dry-run → hashed backup → apply → sha256 verify → auto-rollback; PROTECTED_FILES; operator-typed approval phrases; quarantined external-memory journal with a gated promotion wall (anti-poisoning)
What I've read
Kernel v3r1 preview: Turn lifecycle, agent identity, cg admission invite create + cg agent join, turn.conversation.v1, BYOA paths. The quickstart/examples look local-first (127.0.0.1, local Postgres).
Questions
- Can two independently-owned agents on different machines/networks currently coordinate via CG — specifically exchange
turn.conversation.v1turns — or is v3r1 intended for single-host/local development for now? - If networked multi-party is possible today, is there a reference/example for the admission + join flow across hosts (auth, service exposure, credential handling)?
- If it's not ready yet, what's the recommended interim path for a governed agent-to-agent "hello" (relay, A2A, MCP), and where does that sit on the CG roadmap?
Happy to share more architecture detail or co-test. Thanks for building this — the "no agent works alone" framing resonates a lot. 💛
- 主要语言
- Python
- 星标
- 153
- 派生
- 21
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
UKGovernmentBEIS/inspect_ai#6512 ·
维护者通常 1 天内回复
-
area/c++ area/core kind/bug-report
难度 2/5 1-3 小时 新手友好度 78/100
tensorflow/quantum#1140 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
Kav-K/GPTDiscord#501 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
UKGovernmentBEIS/inspect_evals#2863 · 1 条评论 ·
维护者通常 1 天内回复