Crewspace Create Agent

3. Read adapter-specific docs (example: claude_local).

curl -sS "$CREWSPACE_API_URL/llms/agent-configuration/claude_local.txt" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

4. Compare existing agent configurations in your company.

curl -sS "$CREWSPACE_API_URL/api/companies/$CREWSPACE_COMPANY_ID/agent-configurations" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

5. Discover allowed agent icons and pick one that matches the role.

curl -sS "$CREWSPACE_API_URL/llms/agent-icons.txt" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

6. Draft the new hire config:

• role/title/name
• icon (required in practice; use one from /llms/agent-icons.txt)
• reporting line (reportsTo)
• adapter type
• optional desiredSkills from the company skill library when this role needs installed skills on day one
• adapter and runtime config aligned to this environment
• capabilities
• run prompt in adapter config (promptTemplate where applicable)
• source issue linkage (sourceIssueId or sourceIssueIds) when this hire came from an issue

7. Submit hire request.

curl -sS -X POST "$CREWSPACE_API_URL/api/companies/$CREWSPACE_COMPANY_ID/agent-hires" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "CTO",
    "role": "cto",
    "title": "Chief Technology Officer",
    "icon": "crown",
    "reportsTo": "<ceo-agent-id>",
    "capabilities": "Owns technical roadmap, architecture, staffing, execution",
    "desiredSkills": ["vercel-labs/agent-browser/agent-browser"],
    "adapterType": "codex_local",
    "adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
    "runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}},
    "sourceIssueId": "<issue-id>"
  }'

8. Handle governance state:

• if response has approval, hire is pending_approval
• monitor and discuss on approval thread
• when the board approves, you will be woken with CREWSPACE_APPROVAL_ID; read linked issues and close/comment follow-up

curl -sS "$CREWSPACE_API_URL/api/approvals/<approval-id>" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

curl -sS -X POST "$CREWSPACE_API_URL/api/approvals/<approval-id>/comments" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"## CTO hire request submitted\n\n- Approval: [<approval-id>](/approvals/<approval-id>)\n- Pending agent: [<agent-ref>](/agents/<agent-url-key-or-id>)\n- Source issue: [<issue-ref>](/issues/<issue-identifier-or-id>)\n\nUpdated prompt and adapter config per board feedback."}'

If the approval already exists and needs manual linking to the issue:

curl -sS -X POST "$CREWSPACE_API_URL/api/issues/<issue-id>/approvals" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"approvalId":"<approval-id>"}'

After approval is granted, run this follow-up loop:

curl -sS "$CREWSPACE_API_URL/api/approvals/$CREWSPACE_APPROVAL_ID" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

curl -sS "$CREWSPACE_API_URL/api/approvals/$CREWSPACE_APPROVAL_ID/issues" \
  -H "Authorization: Bearer $CREWSPACE_API_KEY"

For each linked issue, either:

• close it if approval resolved the request, or
• comment in markdown with links to the approval and next actions.

Quality Bar

Before sending a hire request:

• if the role needs skills, make sure they already exist in the company library or install them first using the CrewSpace company-skills workflow
• Reuse proven config patterns from related agents where possible.
• Set a concrete icon from /llms/agent-icons.txt so the new hire is identifiable in org and task views.
• Avoid secrets in plain text unless required by adapter behavior.
• Ensure reporting line is correct and in-company.
• Ensure prompt is role-specific and operationally scoped.
• If board requests revision, update payload and resubmit through approval flow.

For endpoint payload shapes and full examples, read: skills/crewspace-create-agent/references/api-reference.md