this sheet separates the baseline toolkit from branch additions and operational duties. an adapter being present is not the same as a carrier delivery being verified.
give the agent
the thread.
gate the reply.
the catcher accepts json, form posts, and query-string deliveries, then adapts provider payloads into a common message shape.
append messages to jsonl, deduplicate provider ids, retain the raw payload, and track read state separately.
inspect threads, missed calls, call history, voicemail, and imported carrier email through local views.
use agent-friendly commands and structured setup output, or open the local browser launcher for threads and drafts.
single-recipient sms adapters exist for voip.ms, flowroute, and signalwire, behind environment and send authorization checks.
the mcp branch adds fifteen local tools, a javascript sdk, policy and lookup integration, calling code, and a live event timeline.
- 01carrier and number layer
a provider-owned did, carrier account, sip credentials, and the provider's chosen sms delivery route.
- 02persistent host layer
an awake machine holds the sip registration, credentials, catcher, and communication history instead of relying on an ephemeral agent run.
- 03intake and normalization
provider-specific webhook or email input becomes a common message record while preserving the original delivery for inspection.
- 04local state
jsonl messages, read marks, drafts, sent records, imported attachments, and read-only access to the sip client's call database.
- 05agent interfaces
commands and structured output on main; a local stdio mcp server and javascript sdk on the mcp branch.
- 06outbound policy
explicit send authorization on main, with closed-by-default sender policy on the allow branch and outbound calling experiments in callheavy.
provider models and adapters are implemented, but the repository marks provider verification false. real delivery still needs a live account test.
main's optional catcher token permits requests when unset. use a strong token, tls termination, and appropriate network controls in deployment.
the browser launcher defaults to loopback and has no authentication beyond its bind address. do not expose it as a public dashboard.
voip numbers can be rejected by verification-code services. an agent-controlled number does not guarantee otp delivery or device attestation.
bulk lists, schedules, retry queues, and quiet-hours automation are outside the baseline scope. outbound gates are not compliance certification.
messages and attachments are sensitive. operators must choose file permissions, retention, deletion, and backup policies for their own host.