TypeChat
TypeChat is a library that makes it easy to build natural language interfaces using types.
Building natural language interfaces has traditionally been difficult. These apps often relied on complex decision trees to determine intent and collect the required inputs to take action. Large language models (LLMs) have made this easier by enabling us to take natural language input from a user and match to intent. This has introduced its own challenges including the need to constrain the model's reply for safety, structure responses from the model for further processing, and ensuring that the reply from the model is valid. Prompt engineering aims to solve these problems, but comes with a steep learning curve and increased fragility as the prompt increases in size.
TypeChat replaces prompt engineering with schema engineering.
Simply define types that represent the intents supported in your natural language application. That could be as simple as an interface for categorizing sentiment or more complex examples like types for a shopping cart or music application. For example, to add additional intents to a schema, a developer can add additional types into a discriminated union. To make schemas hierarchical, a developer can use a "meta-schema" to choose one or more sub-schemas based on user input.
After defining your types, TypeChat takes care of the rest by:
- Constructing a prompt to the LLM using types.
- Validating the LLM response conforms to the schema. If the validation fails, repair the non-conforming output through further language model interaction.
- Summarizing succinctly (without use of a LLM) the instance and confirm that it aligns with user intent.
Types are all you need!
Getting Started
The TypeScript/JavaScript package requires Node.js 24.22.1 or newer.
Development uses Node.js 24.22.1, pinned in .nvmrc, which includes the
October 21, 2026 security fixes.
Install TypeChat for TypeScript/JavaScript:
npm install typechat
You can also work with TypeChat from source for:
To see TypeChat in action, we recommend exploring the TypeChat example projects. You can try them on your local machine or in a GitHub Codespace.
To learn more about TypeChat, visit the documentation which includes more information on TypeChat and how to get started.
Project direction
GOALS.md defines what belongs in TypeChat, what does not, and what
is still under consideration. It is the primary repository policy for product
scope. Changes require explicit approval from the human project owner,
@robgruen; community interest and AI recommendations do not change it.
Read it before proposing a new direction. Ordinary in-scope maintenance follows
the normal contribution process.
Repository automation experiment
We are experimenting with a gradual transition to a semi-automated repository.
The initial agent-assisted workflow
keeps humans in the loop, while our longer-term goal is to help community
proposals progress from discussion to accepted, reviewed changes with less
manual coordination. Read about the automation experiment
and how to participate.
Status as of 2026-10-30 (UTC): The
latest backlog assessment
completed successfully after the higher execution limits merged through
#490. The
saved draft inventories
21 open issues and 25 open pull requests at the assessment time, with
plain-language next steps and project-direction classifications.
The run used 195 model calls and 387.86 of the main assessment's 400 AI credits.
Detection used a separate 8.82 credits. The inventory is complete, but
verification remains partial: two CI definitions were inaccessible, and no
tests or job logs were checked. The report is not acceptance of work, a
GitHub Copilot code review, or merge approval.
| Milestone | Implemented | Current status |
|---|
| Community-facing automation plan | 2026-10-26 | Documented in AUTOMATION.md. |
| Manual backlog assessment, Copilot guidance, and workflow checks | 2026-10-26 | Merged via #482 on 2026-10-27 (UTC); manual assessment available on main. |
| Assessment model and reasoning effort | 2026-10-26 | GPT-6.1-sol and main-assessment max effort verified in the first live run on 2026-10-27 (UTC). |
| Reproducible workflow compilation | 2026-10-27 | Verified on GitHub: no generated-file drift and 17 passing tests. |
| First live backlog assessment | 2026-10-27 | Completed successfully; 24 issues and 26 PRs enumerated. PR investigation is partial; no dispositions are approved. |
| Clearer report language | 2026-10-27 | Writing guidance merged via #485. The successful October 29 report uses narrative entries and separates evidence from suggestions; human review remains required. |
| Assessment budget | 2026-10-27 | Main-assessment budget raised to 400 AI credits via #485, confirmed in the latest run. Detection remains separately budgeted. |
| Owner-controlled project direction | 2026-10-27 | Policy, assessment guidance, and merged via . The latest draft classifies every item against the pinned policy. Classifications are advisory; full GitHub enforcement still needs verification. |
Implementation dates do not mean a feature is enabled on GitHub. Existing
maintenance and deployment workflows are unchanged. See the
detailed status and
workflow model configuration.
The saved report is a historical snapshot, not today's backlog. Later merges
and decisions do not rewrite it or turn its recommendations into project policy.
Contributing
Start with the project goals and non-goals. Proposals that would
change these boundaries need an owner-approved policy change before their
implementation can be accepted.
Repository automation experiment: We are experimenting with a gradual
transition to a semi-automated repository. The initial agent-assisted workflow
keeps humans in the loop, while our longer-term goal is to help community
proposals progress from discussion to accepted, reviewed changes with less
manual coordination. Read about the automation experiment
and how to participate.
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct.
For more information see the Code of Conduct FAQ or
contact [email protected] with any additional questions or comments.
Website changes
The website source is in site. From the repository root:
npm --prefix site ci
npm --prefix site run build
npm --prefix site run serve
For UI changes, check keyboard navigation, including visible focus in Windows high-contrast themes.
Focus indicators should have at least 3:1 contrast against the adjacent background.
Check reflow at a 320 x 256 CSS-pixel viewport, equivalent to 400% zoom at 1280 x 1024.
Also apply text-spacing overrides: line height of 1.5, letter spacing of 0.12em, word spacing of
0.16em, and paragraph spacing of 2em. The install command must remain readable and its copy button
visible and keyboard-operable. With JavaScript disabled, the command should remain readable and the
inactive copy button should be hidden.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft
trademarks or logos is subject to and must follow
Microsoft's Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.
