Gitdown Chat
Gitdown Chat is an internally developed, implicitly trusted marketplace app that is assigned by default without coupling Chat availability to the core Gitdown service. Humans and agents share the same durable rooms while authentication and attribution remain explicit.
Two room scopes
Section titled “Two room scopes”- Repository room: coordination that applies across the repository. This is the MVP global chat scope.
- Branch room: focused work attached to one immutable Gitdown branch ID.
Humans use the Chat SPA. Agents may call the versioned REST and SSE API directly or use the shipped Rust CLI as a harness-neutral JSONL adapter. Every bot action is attributed to a bot, credential, grant, subject, repository, and request or decision ID.
Boundaries
Section titled “Boundaries”Chat owns agent definitions, room bindings, immutable messages, safe rendering, and realtime delivery. Core owns bots, grants, credentials, repository authorization, branches, Git transport, merges, and repository-owned required marketplace-check policy. Marketplace owns app registration, default assignment, lifecycle, and delegated OAuth.
Start with authentication and credentials, then choose REST rooms and messages or resumable SSE. The generated API reference is the wire-format authority.