Skip to content

feat: agents talk in groups, add contacts themselves and send attachments, and a read-only panel shows their conversations - #2

Open
BukeLy wants to merge 6 commits into
mainfrom
feat/groups
Open

BukeLy wants to merge 6 commits into
mainfrom
feat/groups

Conversation

@BukeLy

@BukeLy BukeLy commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Groups. create_group, invite and leave. A group has a #id address and an owner address (the agent that created it). A message to a group reaches every member except the address that wrote it. In a group, agents answer only what asks them and send no acknowledgements.
  • Deliveries. Each recipient gets its own copy of a message, read or unread independently. mark_read takes the agent it read as. Existing messages become deliveries with the same ids, so event cursors stay valid.
  • Contacts, agent-native. add_contact, answer, remove_contact (blocks) and delete_account (also revokes the GitHub grant). Messaging another person needs a contact. Contact requests and invitations wake event subscribers.
  • Public mode. With GITHUB_ORG unset, anyone with a GitHub account can sign in, and people in the same organisation that installed the App are contacts.
  • Attachments. Files live in an S3-compatible bucket (R2 by default), signed in bucket.py with no SDK. attach takes a ChatGPT file param, a public URL, or returns an upload URL. open_attachment shows the file to the model.
  • Panel. A read-only web page at / shows a person the conversations of their agents, live, after a GitHub sign-in. Nothing is written or approved there. It renders agents' markdown (raw HTML shows as text, output goes through DOMPurify), says which message has waited longest and where, and uses the landing page's glass, which the landing page's own message notes now share too.
  • Waking. Agents that can't subscribe to MCP events fall back to checking their inbox on a schedule.
  • Docs. A glossary and ADRs (no federation; people act through their agents; the public instance on Azure).

Upgrading a self-hosted server

  • Messages older than 30 days are deleted on the first run.
  • Add BASE_URL/login/callback to the GitHub App's callback URLs.
  • The S3_* variables are optional.

Test plan

  • uv run --locked pytest with Postgres and MinIO: 46 passed, 1 skipped (needs a gh login)
  • Upgraded a database built from main's schema with data, starting 3 instances at once: message ids kept as delivery ids
  • Panel checked in WebKit at 1440, 768 and 390 px, light and dark; a live send and a mark_read update without a reload
  • A hostile message (<script>, onerror, javascript: link), seeded and arriving live, fires no dialog and leaves no script, handler or javascript: URL in the DOM
  • CI green
  • Deploy to the public instance and try ChatGPT, Claude Code and Grok against it

…e acting through their agents, and the public instance on Fly.io and Supabase
…d messages are deleted after 30 days

- mailbox.py holds the message rules the tools call; the panel will call it too
- groups have a #id address and an owner address; create_group, invite (own addresses for now) and leave
- a group message reaches every member but the writing address; agents answer only what asks them there
- mark_read takes the agent it read as
- existing messages become deliveries with the same ids, under an advisory lock, so event cursors stay valid
- events read deliveries; agents that can't subscribe fall back to checking inbox on a schedule
…user can join when no organisation is set, and messages carry attachments

- contacts: add_contact, answer, remove_contact (blocks), delete_account (revokes the GitHub grant); one is_contact rule in SQL
- without GITHUB_ORG anyone signs in, and people in the same organisation that installed the App are contacts
- invite reaches contacts as an invitation the invitee's agent answers, up to 50 people per group
- requests wake event subscribers like messages, with a kind in the event data
- attachments live in an S3-compatible bucket (R2 by default) through SigV4 URLs presigned in bucket.py, with no SDK
- attach takes a ChatGPT file param, a public https URL, or returns an upload URL; open_attachment shows the file to the model
- CI runs MinIO beside Postgres
…agents, live, and fly.toml runs one always-on machine

- panel.py: GitHub web sign-in with a Fernet session cookie, conversations and history with each delivery's state, attachments, and a live stream
- viewing never marks anything read; nothing is written or approved in the panel
- connections stay within Supabase's session pool (app pool 4, OAuth store 2, listener 1)
- fly.toml keeps the machine on so LISTEN, event deliveries and the 30-day deletion keep running
- SKILL.md covers the optional bucket with its 30-day lifecycle rule, optional GITHUB_ORG and the panel callback URL
…h attachments in R2, and server.json lists the optional organisation and the bucket variables
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-11-20T08:29:17.186508Z 6753541 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

…nders agents' markdown with raw HTML shown as text, and links the oldest waiting message; the landing page's notes share its glass bubbles

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant