Skip to content

feat(marketing): backfill missing proactive agents on /agents route#27

Merged
khaliqgant merged 2 commits into
AgentWorkforce:mainfrom
kjgbot:feat/marketing-agent-backfill
Jul 19, 2026
Merged

feat(marketing): backfill missing proactive agents on /agents route#27
khaliqgant merged 2 commits into
AgentWorkforce:mainfrom
kjgbot:feat/marketing-agent-backfill

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Jul 18, 2026

Copy link
Copy Markdown
Member

What changed

  • Added the seven missing customer-facing proactive agents to the typed marketing catalog: Cloudflare Monitor, Daytona Monitor, GCP Watcher, Neon Monitor, Inbox Buddy, Joke Bot, and Linear Slack.
  • Added typed integration labels for Cloudflare, Daytona, Google Cloud, Gmail, Neon, and Telegram.
  • Kept every marketing slug identical to its AgentWorkforce/agents directory. Inbox Buddy and Joke Bot remain one catalog entry each because their personas are dual-transport Slack/Telegram agents, not separate Telegram variants.
  • Left agent artwork on the existing monogram fallback because these new directories do not ship the full banner / card / card-sm set expected by AgentArt, and artwork is owned by MK-2.

Why

The /agents marketing 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.
  • Catalog invariant check — 14 unique slugs, all required entries present, no slug/directory mismatches.
  • git diff --check — passed.

Authored by the mk-1-marketing-backfill launch-prep agent.


Summary by cubic

Backfilled the marketing catalog so the /agents route 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

    • Added agents: Cloudflare Monitor, Daytona Monitor, GCP Watcher, Neon Monitor, Inbox Buddy, Joke Bot, Linear Slack.
    • Added INTEGRATION_LABELS for cloudflare, daytona, gcp, google-mail, neon, telegram.
    • Kept slugs aligned with AgentWorkforce/agents; Inbox Buddy and Joke Bot remain single entries for dual Slack/Telegram.
    • Left artwork on monogram fallback until full assets are available.
  • Bug Fixes

    • Set daytona-monitor trigger kind to event to match other hybrid entries.
    • Added personaFile: 'persona.json' to all seven new agents to match the persona.json + agent.ts layout.

Written for commit 2be999e. Summary will update on new commits.

Review in cubic

@cursor

cursor Bot commented Jul 18, 2026

Copy link
Copy Markdown

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.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread web/lib/agents.ts Outdated
'Reports allocation jumps without mutating Daytona resources.',
],
trigger: {
kind: 'schedule',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
kind: 'schedule',
kind: 'event',

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The 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.

Changes

Agent catalog expansion

Layer / File(s) Summary
Integration contracts and labels
web/lib/agents.ts
The Integration union and INTEGRATION_LABELS mapping add Cloudflare, Daytona, GCP, Google Mail, Neon, and Telegram.
New agent definitions
web/lib/agents.ts
AGENTS adds cloudflare-monitor, daytona-monitor, gcp-watcher, neon-monitor, inbox-buddy, joke-bot, and linear-slack with trigger, integration, runtime, input, and art settings.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Poem

A rabbit checks the clouds up high,
While neon glows and jokes fly by.
Gmail whispers, Slack bells ring,
New agents hop on every thing.
Six new keys make pathways bright! 🐇

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title accurately summarizes the main change: backfilling missing proactive agents on the /agents route.
Description check ✅ Passed The description is directly related to the changeset and explains the added agents, labels, fixes, and verification.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread web/lib/agents.ts
Comment on lines +259 to +261
slug: 'cloudflare-monitor',
personaId: 'cloudflare-monitor',
dir: 'cloudflare-monitor',

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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.
@khaliqgant
khaliqgant merged commit 31c786e into AgentWorkforce:main Jul 19, 2026
3 checks passed
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