about sheet. what kind of software heyphony is, and how the repository's branches fit together.
jerryrigged
on purpose.
heyphony started from a concrete question: what does it take to give an ai agent a phone number of its own without inventing a parallel telephone system?
the answer is a practical adapter around carriers, sip clients, webhooks, local files, and agent tools. the main branch holds the baseline inbox and management workflow. the mcp branch is the broadest integrated tree, adding structured tools, lookup and allow policy, calling code, and a live voice-and-text timeline.
ordinary telephony, made readable to an agent.
other branches explore policy, lookup, calling, deployment, forwarding, devices, omnichannel intake, and meetings. they are not all equally complete, and this site labels them accordingly.
the toolkit and its communication history live with your host. your carrier account remains a separate, explicit dependency.
noninteractive setup and structured output let an agent discover missing information instead of stalling on a terminal prompt.
the repository describes individual versions converting to mit after two years. current source availability is not a blanket open-source claim.