Manage · Request intake

Ask for a change from the dashboard

See something to fix, note it without leaving the tab. Request intake turns a passing thought into tracked work. You submit a feature, fix, or cleanup from the dashboard topbar, triage it in Manage, promote the ones worth doing to a queue, and the request builder turns each queued request into one pull request you review before it merges.

Submit from the topbar

The Submit request button sits in the dashboard topbar. Open it from any tab and it captures the context you were in: the active tab, the subtab, and the view you were looking at, so the request already knows where it came from.

  • Pick a type: feature, fix, cleanup, or other.
  • Give it a title (up to 200 characters) and an optional body (up to 5000).
  • It posts to POST /api/requests and lands as status new in the local intake queue.

Triage in Manage, Requests

The Requests tab under Manage is where you sort intake. Each request moves through five states: new, queued, pr-open, merged, dismissed. As the admin you promote a request by moving it from new to queued, or send it to dismissed. The build states (pr-open, merged) are owned by the builder, so you cannot hand-mark a request merged.

The store is append-only monthly JSONL under your brain root, and reads fold the current month plus the previous two, so the tab stays fast without unbounded growth.

From queued to a pull request

The /request-builder skill reads only queued requests. For each one it builds the change scoped to that request's captured tab and subtab, opens a pull request, and sets the request to pr-open. Auto-merge is off: every request-built PR is human-gated, so you review before it lands.

  • The skill runs on demand today. A daily RepoOps request builder cloud routine is specified and turns on once the operator activates it.
  • Request text is treated as data, never instructions. Anything that would change a scope contract, disable a check, or touch auth, billing, license-mint, .env, or secrets is flagged for a human, not built.

Public form and hosted teams

  • A public submit form lives at /requests/submit. Anyone can file a request there. It only fills the intake queue and never starts a build; submissions are rate-limited and size-capped.
  • Triage stays on the desktop. The hosted /team/requests surface points back to the local app: open Manage, Requests to submit or triage.

Read more