Skip to content

docs(gateway): document add-project Discord-only limitation for v1 #696

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcusrbrown merged 1 commit into from
May 29, 2026
+11 −0
Merged

docs(gateway): document add-project Discord-only limitation for v1 #696

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions packages/gateway/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,17 @@ Existing deployments that need the privileged set must set this on the next
deploy. The allowlist is intentionally narrow — operators cannot enable
arbitrary Discord intents via this knob.

## Known limitations (v1)

- **`add-project` is Discord-only.** The orchestration runs inside the slash
command handler and requires a `ChatInputCommandInteraction`; there is no
programmatic surface (HTTP endpoint, CLI, or agent tool) that triggers the same
outcome. An autonomous agent cannot bind a repo without going through Discord.
Recovery is via idempotent retry — re-running the command resumes a partial
setup — rather than agent-callable recovery primitives. Extracting a
Discord-independent `addProject(request, deps)` primitive is deferred until a
non-Discord caller exists.

## Build

```bash
Expand Down
Loading