Skip to content

Super Agents (3+4/5): live screenshot + landing section + single-worker registry - #83

Merged
mahimairaja merged 1 commit into
mainfrom
feat/superagents-screenshot
Jul 10, 2026
Merged

Super Agents (3+4/5): live screenshot + landing section + single-worker registry#83
mahimairaja merged 1 commit into
mainfrom
feat/superagents-screenshot

Conversation

@mahimairaja

Copy link
Copy Markdown
Owner

Phases 3 and 4 combined (a PNG-only PR has no standalone value; see docs/superpowers/superagents-loop.md).

  • Captured the real /agents dashboard mid-handoff (Concierge -> Property -> Scheduling, Scheduling active) into web/public/screenshots/agents.png, populated via POST /agent-state (real UI, seeded state).
  • web/src/pages/index.astro: a 'One call, a team of specialists' section with the screenshot in a browser frame.
  • docker-compose.yml: WEB_CONCURRENCY=1 for the backend. The live-agent registry is in-process; with the default 2 gunicorn workers the console SSE and the agent-state POST hit different registries and the live graph flickers. A single worker keeps a self-hosted node consistent (verified: live SSE updates now apply in order).

Gate: web pnpm build clean; visual review of the /agents page (live handoff) and the landing section done in a headed browser.

…gistry

Phase 3+4 of the Super Agents loop. Captures the real /agents dashboard (the
Concierge -> Property -> Scheduling handoff, live) and adds a 'One call, a team
of specialists' section to the marketing page, screenshot in a browser frame.

Also pins the backend to a single gunicorn worker in the local stack: the
live-agent registry (src/runtime/live_agents.py) is in-process, so with the
default two workers the console's SSE and the worker's agent-state POST land on
different registries and the graph flickers. One worker keeps a self-hosted
node consistent; plenty for a solo realtor.
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mahimairaja, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2a578f95-b9a9-4cd5-a34d-f775e68490ac

📥 Commits

Reviewing files that changed from the base of the PR and between b4d77b8 and bbc2406.

⛔ Files ignored due to path filters (1)
  • web/public/screenshots/agents.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docker-compose.yml
  • web/src/pages/index.astro
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/superagents-screenshot

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

Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 10, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
superrealty bbc2406 Jul 10 2026, 05:12 PM

@mahimairaja
mahimairaja merged commit ad99982 into main Jul 10, 2026
7 checks passed
@mahimairaja
mahimairaja deleted the feat/superagents-screenshot branch July 10, 2026 17:12
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