Problem
When creating messages or comments via the CLI, all project members are automatically subscribed and notified. There is no way to post silently.

This is critical for bot/agent use cases where automated posts should not generate notifications for the entire team.

Current behavior
basecamp message --subject "Update" --content "..." --in 17525144 --json

→ All 14 project members auto-subscribed and notified

Even using the Basecamp API directly with subscribers: [bot_person_id], all project members are still auto-subscribed when a message becomes active.

Tested approaches (all failed)

1. API POST with subscribers: [bot_id] → All members still subscribed

2. API POST with subscribers: [] → All members still subscribed

3. Create as draft → remove subscribers → publish → Publishing re-adds all members

Expected behavior
A --silent or --no-notify flag that prevents notifications:

basecamp message --subject "Bot update" --content "..." --in 17525144 --silent --json

→ Message published, no notifications sent

The Basecamp 3 API docs mention subscribers as a parameter on message creation that should control notification recipients. This doesn't seem to work in Basecamp 4, or the CLI doesn't pass it through.

Workaround

Post message

ID=$(basecamp message --subject "..." --content "..." --in --json --quiet | jq '.id')

Remove all subscribers except bot

basecamp subscriptions remove $ID --people "id1,id2,..." --in
This prevents notifications for subsequent comments but cannot prevent the initial creation notification.

Use case
AI agents (like Claude, Codex) posting automated updates, research findings, or logs to Basecamp. These posts are informational records, not things that should ping the whole team.

Environment
basecamp CLI v0.2.1, Basecamp 4 API, OAuth 2.1 authentication