Symphony.run

Write programs you can talk to, powered by conversational functions

Advanced
Screenshot of Symphony.run, Write programs you can talk to, powered by conversational functions

What is Symphony.run?

Symphony.run is a chatbot builder tool that writes programs you can talk to, powered by conversational functions. Symphony is a developer tool for building conversational programs: you write TypeScript or Python functions, and a natural language layer routes user requests to the right functions at runtime, so users can state goals in plain language instead of clicking through fixed flows.

Symphony is a development tool built around a single proposition: programs should be something you can talk to. Rather than assembling a rigid menu of buttons or a fixed conversational flow, developers write functions (the homepage shows examples such as search_contacts.ts, get_events.ts, search_places.py and suggest_event.ts) and the system decides which of them to call based on what the user says. The result is a natural language interface layered over real code and real data, with the model handling intent and orchestration while the underlying functions do the actual work. The homepage example captures the intended experience. A request like getting drinks with Dan tomorrow evening after studio is expressed casually, in a single sentence, yet it depends on several capabilities at once: looking up a contact, checking a calendar, finding a place, and proposing an event. In Symphony, those capabilities exist as discrete typed functions in the languages a developer already writes, and the conversational layer stitches them together at runtime. Instead of predicting every possible user journey in advance, the developer exposes tools and lets the conversation route between them. This places Symphony in the emerging class of tool-calling and agent orchestration frameworks, but with an emphasis on the conversational program as the product rather than a library you bolt on. It suits developers and product teams building assistants, scheduling experiences, contact search, or any interface where users state goals in their own words and expect the software to figure out the steps. Teams weighing it against general purpose agent frameworks should note that Symphony is opinionated about functions as the unit of capability. The practical draw is that the code stays ordinary. Functions live in TypeScript and Python files, which keeps logic testable and versioned like any other part of the repository, while the conversational layer handles routing. The project is open source, with a repository and a Discord community linked from the site, and documentation and a blog cover the setup path. The homepage is deliberately minimal and does not publish pricing tiers, so buyers should confirm commercial terms before committing production workloads.

How do you use Symphony.run?

  1. 1Read the documentation first
    Start with the docs to understand how conversational programs are structured and what the runtime expects from your functions before writing any code.
  2. 2Write your first functions
    Create small, single purpose functions in TypeScript or Python, following the pattern of examples like search_contacts.ts or search_places.py on the homepage.
  3. 3Connect functions to the conversational layer
    Register the functions so the program can route a natural language request to the appropriate one, including multi-step requests that need several functions in sequence.
  4. 4Test with real conversational phrasing
    Try requests written the way a user would actually speak them, such as combining a person, a time and a place in one sentence, and check which functions get called.
  5. 5Join the community and follow updates
    Use the Discord and the blog to ask questions, see how other developers structure their functions, and keep track of changes to the project.

Pros and cons

Pros

  • Functions stay in ordinary TypeScript and Python files, so logic is versioned and testable like the rest of a repositoryAI
  • The homepage example shows multi-step intent handling: contact lookup, calendar checks and place search in one sentenceAI
  • Open source repository and a public Discord give developers a way to inspect and discuss the internalsAI
  • Documentation and a blog are both linked, giving newcomers a defined starting pathAI

Cons

  • No pricing, plan tiers or commercial terms are published on the homepage, which makes budgeting difficultAI
  • The homepage shows only a handful of sample functions and no full reference for how routing decisions are madeAI
  • Success depends heavily on how well functions are named and scoped, which is a skill rather than a defaultAI
  • Little public information on production concerns such as latency, rate limits or failure handlingAI

How much does Symphony.run cost?

Support

Support runs through the public Discord community linked from the homepage, alongside documentation and a blog. No formal support tiers or service level commitments are described on the site.

Learn more

Features

Symphony lets developers define capabilities as functions written in TypeScript or Python and then expose them through a conversational interface. The system interprets a natural language request and selects the functions needed to fulfil it, including requests that require several functions in sequence, such as combining a contact lookup, a calendar check and a place search into one action.

Frequently asked questions about Symphony.run

  • How do you use Symphony.run?
    The walkthrough on this page covers 5 steps: 1. Read the documentation first 2. Write your first functions 3. Connect functions to the conversational layer 4. Test with real conversational phrasing 5. Join the community and follow updates.
  • What platforms does Symphony.run support?
    Symphony.run is available on Web App.
  • What are the limitations of Symphony.run?
    No pricing, plan tiers or commercial terms are published on the homepage, which makes budgeting difficult. The homepage shows only a handful of sample functions and no full reference for how routing decisions are made. Success depends heavily on how well functions are named and scoped, which is a skill rather than a default.

Status

StatusActive
Views0
Outbound clicks0
Added10/21/2026

Platforms

Web App

Pricing

Free