Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

basecamp-connect

Drive your own Claude Code session from Basecamp. Starts the local connector (basecamp connect), which listens to the account's event feed as a Basecamp agent and prints one line per trusted request: a mention, an assignment, a comment on a thread the agent follows, a boost on something it wrote. This session acknowledges each one that asks for something within seconds (a boost in its own words), picks the repo for the project, and hands the request to a background subagent that reads the context, does the work with your settings and tools, and replies as the agent. The session stays free to take the next request, and you can keep using it. Also connects an agent to this computer and manages its setup: the agent's credential (basecamp auth agent connect), who may give it work, and which projects it serves (basecamp connect setup), plus status and doctor. Use when asked to connect an agent, drive agents from Basecamp, watch Basecamp for an agent's mentions, start or stop the connector,

basecamp · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add basecamp/basecamp-cli --skill basecamp-connect

About this skill


name: basecamp-connect description: | Drive your own Claude Code session from Basecamp. Starts the local connector (basecamp connect), which listens to the account's event feed as a Basecamp agent and prints one line per trusted request: a mention, an assignment, a comment on a thread the agent follows, a boost on something it wrote. This session acknowledges each one that asks for something within seconds (a boost in its own words), picks the repo for the project, and hands the request to a background subagent that reads the context, does the work with your settings and tools, and replies as the agent. The session stays free to take the next request, and you can keep using it. Also connects an agent to this computer and manages its setup: the agent's credential (basecamp auth agent connect), who may give it work, and which projects it serves (basecamp connect setup), plus status and doctor. Use when asked to connect an agent, drive agents from Basecamp, watch Basecamp for an agent's mentions, start or stop the connector, or change who can give the agent work or which projects it serves. triggers:

  • /basecamp-connect
  • connect an agent
  • drive agents from basecamp
  • watch basecamp for agent commands
  • start the connector
  • stop the connector
  • is the connector running
  • set up the connector
  • basecamp connect setup
  • basecamp auth agent connect
  • serve a project
  • who can give the agent work
  • connector not ready
  • basecamp connect status
  • basecamp connect doctor

/basecamp-connect: drive your agent from Basecamp

Someone @mentions the agent in Basecamp (or assigns it a card or to-do). This session acknowledges it as the agent within seconds, a background subagent does the work in the right repo with your own Claude Code setup, and the agent replies in place.

Three pieces:

  • The agent: a Basecamp person of its own, owned by you, connected to this computer under a CLI profile (often named after the agent).
  • The connector: basecamp connect -P '<profile>'. It listens to the account's event feed as the agent, checks each event against who may give the agent work and which projects it serves, and prints one line per trusted request. It does nothing else: no workers, no acknowledgements, no replies.
  • This session: the orchestrator. It watches those lines, acknowledges each request, chooses the repo, and dispatches one background subagent per request. It never does the work itself.

Claude Code only. The connector runs on Linux and macOS.

Running the connector

1. Start it, and watch its output

Only one connector per agent can run at a time. If it's already running elsewhere, it refuses to start and says so: tell the person, and don't start a second.

Start it in the background with the Bash tool (run_in_background: true), and note the output file the harness reports:

basecamp connect -P '<profile>'

It runs until stopped. Its folder doesn't matter: every subagent works in the repo you choose for it. Read the output once after a few seconds. You should see connector: running in its log. If it exited instead, explain the error (see When the connector stops), and stop. If it says could not get the agent's token yet, Basecamp's token endpoint is rate-limiting it or having trouble: it waits as long as it says and tries again on its own. Tell the person, leave it running, and arm the monitor as usual. Restarting it doesn't help.

Then arm a persistent monitor on that file with the Monitor tool (persistent: true), replaying from the start so nothing that arrived between the start and the monitor is missed:

tail -f -n +1 '<connector-output-file>' | grep --line-buffered -F '"type":"request"'

Single-quote the path, as with every other value.

Each notification is one request: handle it with For each request. A request that arrives while you're waiting on the person is not their reply.

The connector starts from the present. Anything asked more than a minute before it started is not picked up. If someone says the agent ignored them, that's the first thing to check.

2. The request line

{"type":"request","event_id":123,"event_type":"comment_created","trigger":"mentioned",
 "recording":{"bucket_id":456,"project_name":"BC5 Calendar","recording_id":789,"type":"Comment",
              "title":"Fix the date picker","url":"https://3.basecamp.com/999/buckets/456/recordings/789"},
 "reply_to":{"kind":"comment","recording_id":700},
 "requester_id":1001,"requester_name":"Jorge Manrubia","role":"operator","owner":true,"acknowledge":true,
 "go":false,"ask":{"title":"","content":""},"content":"<p>fix the date picker</p>","content_updated_at":"..."}
  • trigger: why it reached you.
    • mentioned: someone @mentioned the agent.
    • assigned: the operator, or someone they opted in, assigned it a card, to-do or step. Only when the recording's events show this assignment added the agent, and the agent is still assigned.
    • subscribed: a new comment on a thread the agent follows, with no mention.
    • completed: something completed in a project it watches.
    • boosted: a boost on the agent's own post.
  • acknowledge: true when a person asked for something. False for subscribed, completed and boosted, context unless a go.
  • recording: what the event is about. bucket_id is the project, project_name its name. url works with every command below.
  • reply_to: where the answer goes. kind comment means a comment on recording_id (already chosen for you). kind chat_line means a line in the Campfire recording_id.
  • requester_id: the person who asked. Mention them on failure, except in Campfire. requester_name is their name when they wrote the recording; it's missing for an assignment someone else's recording carries.
  • role: operator (the operator, or someone named with --allow) o
Read the complete source ↗