Skip to content

feat(inbox): surface agents waiting for input - #2992

Draft
asantos00 wants to merge 1 commit into
devswha:mainfrom
asantos00:feat/agent-inbox
Draft

asantos00 wants to merge 1 commit into
devswha:mainfrom
asantos00:feat/agent-inbox

Conversation

@asantos00

@asantos00 asantos00 commented Nov 5, 2026 •

Copy link
Copy Markdown

Change

Refs #2991.

Adds a mobile-first Inbox in the header for agent panes that currently need human input.

  • projects the existing all-PC Agents roster and authoritative displayed blocked state
  • orders items by PC roster and each PC's existing Activity order
  • shows the agent's reported waiting kind and decision context without reading transcripts, polling prompts, or sending input
  • identifies the PC, workspace, tab, pane, and agent
  • opens the exact pane directly in Chat, where the existing prompt card remains the decision surface
  • updates live as blocked panes resolve, with loading, empty, and offline states
  • includes English, Korean, Japanese, and Simplified Chinese UI, demo coverage, tests, design notes, and a changelog entry

Design references: Codex's focused agent threads, Linear Inbox's attention queue and close-to-work actions, AlphaAgent Inbox's context-before-navigation, and Agent Cockpit's descriptive approval cards. This deliberately adds no risk labels, read state, snooze state, completion history, or server contract.

This is a draft because CONTRIBUTING asks for maintainer agreement on the feature request before a feature PR is considered ready.

Visuals

Fictional demo data only.

DesktopMobile
Desktop Ovis Inbox showing one agent permission request with context and an Open chat action Mobile Ovis Inbox sheet showing the same permission request and direct chat action

Validation

Passed:

  • bun test src/lib/agentInbox.test.ts src/components/AgentInbox.test.tsx src/lib/i18n.test.ts src/conventions.test.ts — 39 passed
  • bun run typecheck
  • bun run build
  • bun run build:site
  • git diff --check
  • manual browser QA at 1440×900 and 390×844 against the fictional demo
  • verified Inbox → exact blocked Chat navigation
  • axe audit of the open mobile Inbox found no Inbox-specific violation

Attempted:

  • bun run check fast — generated types, generated themes, typecheck, and build passed; the repository-wide unit lane failed in unrelated environment-sensitive server/relay/script tests (218 failures, including repeated 60-second relay proof timeouts). Focused Inbox, i18n, and convention tests pass independently.

Not run:

  • herdr integration/browser lanes; this change has no server or wire-contract change and browser behavior was exercised against the isolated demo.

@coderabbitai

coderabbitai Bot commented Nov 5, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@devswha

devswha commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Heads-up: this repository now asks every contributor to sign a Contributor License Agreement once. You keep the copyright of your work; the CLA gives the maintainer the licence to use it.

To sign, comment on this PR with exactly:

I have read the CLA Document and I hereby sign the CLA

One signature covers this and every later pull request. Nothing else about this PR changes, and a "CLA" check will appear on your next push.

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.

2 participants