RecruiterStack v2: 10-agent swarm with Paperclip dashboard + Forge runtime - #1
Open
jbellsolutions wants to merge 3 commits into
Open
jbellsolutions wants to merge 3 commits into
jbellsolutions wants to merge 3 commits into
Conversation
…ntime The repo now leads with the 10 agents, the NL flow ends in Activate Agents, and Paperclip auto-bootstraps as the local dashboard at localhost:3100. - 10 agent specs in agents/<slug>/SPEC.md (single source of truth) - config/pain-to-agent.json maps the 13 problem categories -> agent slugs - orchestrator/ wires the diagnosis to Paperclip (auto-bootstrap, register, fallback) - paperclip/ ships a plugin with the recruiting org chart (auto-generated from SPEC.md) - /api/plan-chat now returns recommendedAgents - /api/spawn endpoint kicks off the spawn into Paperclip with graceful fallback - /plan UI gets an Activate Agents card that opens the dashboard - README rewrite leads with the 10 agents and 60-second flow Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
You have used all of your free Bugbot PR reviews. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
Keeps response shape consistent so the planner UI shows the Activate Agents card even when ANTHROPIC_API_KEY isn't set, as long as the user has selected problems in the sidebar. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Endpoint is POST /api/companies/{companyId}/agents (not /api/agents)
- camelCase fields: reportsTo, budgetMonthlyCents, adapterType, adapterConfig
- adapterType "claude_local"; adapterConfig points cwd at repo root and
instructionsFilePath at agents/<slug>/SPEC.md
- dangerouslySkipPermissions defaults to false (safe)
- role normalizes to "general"; title goes in title; staffing role goes in
capabilities. Schema source: paperclipai/paperclip packages/shared/src/validators/agent.ts.
- Adds GET /api/companies fetch with PAPERCLIP_COMPANY_ID env override and
preference for a company named "RecruiterStack" before falling back to
the first active one.
Live-tested: HTTP 201 from a running paperclipai instance; agent appeared
in the dashboard with correct adapter config.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
localhost:3100.agents/<slug>/SPEC.mdare the single source of truth;paperclip/agents/*.jsonare auto-generated from them vianpm run build:paperclip.orchestrator/(TypeScript) auto-bootstraps Paperclip vianpx paperclipai onboard --yes, registers agents over its HTTP API, and emits a copy-pasteable fallback per agent if Paperclip isn't reachable./api/plan-chatnow returnsrecommendedAgents(computed fromselectedProblems+ priority viaconfig/pain-to-agent.json);/api/spawnis the new endpoint the planner calls when the user clicks Activate.Test plan
npm install && npm run devboots the planner on:3000/planclaiming 2 specific pain points (e.g. "candidate ghosting" + "recruiter productivity") → confirm an "Activate Agents" card appears with the right subset checkednpx paperclipai onboard --yesinstructionsnpx paperclipai onboard --yesseparately → click Activate again → confirm dashboard opens atlocalhost:3100with the agents staffednpm run build:paperclipregenerates the 10 JSON files cleanlynpx tsc --noEmitandnpx next buildboth pass🤖 Generated with Claude Code