feat(marketing): backfill missing proactive agents on /agents route#27
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Code Review
This pull request introduces several new integrations (including Cloudflare, Daytona, GCP, Neon, and Telegram) and adds seven new monitoring and conversational agents to the catalog. The review feedback points out that the 'daytona-monitor' agent should have its trigger kind updated from 'schedule' to 'event' to align with other hybrid agents and ensure it is correctly represented in the UI.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| 'Reports allocation jumps without mutating Daytona resources.', | ||
| ], | ||
| trigger: { | ||
| kind: 'schedule', |
There was a problem hiding this comment.
The daytona-monitor agent is configured with kind: 'schedule', but its trigger also reacts to webhook events (sandbox.created and sandbox.state.updated). To be consistent with other hybrid agents in this catalog (such as gcp-watcher, neon-monitor, and joke-bot), its kind should be set to 'event'. This ensures it is correctly labeled as an "Event" trigger in the UI.
| kind: 'schedule', | |
| kind: 'event', |
📝 WalkthroughWalkthroughThe integration model and labels include six additional services. The exported agent catalog adds seven agents for monitoring, inbox assistance, jokes, and Slack-based Linear collaboration, with configured triggers, integrations, runtime, inputs, and visual metadata. ChangesAgent catalog expansion
Estimated code review effort: 3 (Moderate) | ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 43517f7bd5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| slug: 'cloudflare-monitor', | ||
| personaId: 'cloudflare-monitor', | ||
| dir: 'cloudflare-monitor', |
There was a problem hiding this comment.
Point the new launch targets at persona.json
This entry, like all six new entries below it, omits personaFile, so personaUrl() falls back to <dir>/persona.ts (web/lib/agents.ts:621-623). These agents use the documented persona.json + agent.ts layout (web/content/docs/7.1.1/proactive-agents.mdx:16-24), making the primary “Launch agent” CTA on every newly added detail page reference a nonexistent persona definition instead of the deployable JSON file.
Useful? React with 👍 / 👎.
…personaFile pointer Addresses two review findings on the marketing catalog backfill: - daytona-monitor.trigger.kind: schedule → event, matching the other hybrid entries (gcp-watcher, neon-monitor, joke-bot) that also react to webhook events on top of a scheduled sweep. - personaFile: 'persona.json' added to the seven new customer-facing proactive agent entries. The personaUrl() fallback pointed at <dir>/persona.ts by default, but these agents ship the persona.json + agent.ts layout documented in web/content/docs/7.1.1/proactive-agents.mdx. Manual follow-up commit after the mk-1-pr27-review-fix codex agent went idle without pushing.
What changed
AgentWorkforce/agentsdirectory. Inbox Buddy and Joke Bot remain one catalog entry each because their personas are dual-transport Slack/Telegram agents, not separate Telegram variants.banner/card/card-smset expected byAgentArt, and artwork is owned by MK-2.Why
The
/agentsmarketing route exposed only 7 agents while the source catalog ships 14 customer-facing proactive agents. This backfills the missing entries so the gallery, static detail routes, sitemap, and one-click deploy links cover the complete catalog.Verification
npm test— 13 test files passed, 93 tests passed.npm run build— production build and TypeScript checks passed; all 14 agent detail routes were statically generated.git diff --check— passed.Authored by the
mk-1-marketing-backfilllaunch-prep agent.Summary by cubic
Backfilled the marketing catalog so the
/agentsroute now shows all 14 customer-facing proactive agents. Adds seven missing agents, typed labels for new integrations, and fixes Daytona Monitor trigger and persona file pointers.New Features
INTEGRATION_LABELSforcloudflare,daytona,gcp,google-mail,neon,telegram.AgentWorkforce/agents; Inbox Buddy and Joke Bot remain single entries for dual Slack/Telegram.Bug Fixes
daytona-monitortrigger kind toeventto match other hybrid entries.personaFile: 'persona.json'to all seven new agents to match thepersona.json+agent.tslayout.Written for commit 2be999e. Summary will update on new commits.