Announcing Jargon's IDE

Jonathan Burstein

Jonathan Burstein

Announcing Jargon's IDE
Available in beta for Rasa only
ide cms hero image

We’re very excited to announce the beta release of our IDE for Rasa apps. The IDE allows enterprise teams to build and manage the many interconnected conversational app components, such as stories, intents, responses, entities, forms, etc. By combining IDE and CMS capabilities, Jargon helps keep teams organized and significantly boosts productivity.

You can watch a brief demo here.

Why we built an IDE for conversational apps

Building and scaling a conversational app is a unique challenge. There are many app components scattered across multiple files, making it difficult to find what you’re looking for, or to see how the pieces fit together. To add to the complexity, stories – in many ways the core of Rasa – are primarily defined in symbolic terms using intent and action labels, instead of user-facing language. To comprehend what the story is trying to achieve, you need to manually find what each label refers to – a particular challenge when components are scattered across multiple files. Likewise, when authoring a story it’s easy to get similar labels confused and choose one that wasn’t intended.

When making changes to a conversational app, it can also be difficult to determine how a given artifact is used and what impact changing it might have. Intents and responses (or custom actions) are often referenced by more than one story or rule. Making a small change to an intent might make sense for one story, but could dramatically change the meaning of others. Finally, without editor assistance many kinds of errors – from simple typos to complex semantic errors – aren’t discoverable until model training time at best, and sometimes not until the new version of the application goes live and your users start receiving unexpected results.

The need for organization of app components

The principles guiding Jargon offer solutions to these issues. Everything in Jargon is presented as categorized components (stories, intents, responses etc.) that are easy to navigate, instead of as raw files. As you build or review elements of your application, Jargon surfaces the key context necessary to boost comprehension of the application as a whole, and makes it quick and easy to navigate across the numerous interconnected components. Taking advantage of its knowledge of your entire application, Jargon detects errors (both simple and complex) and provides pertinent suggestions to speed up application development.

Boost productivity and stay organized

Here are some of the core features in Jargon that enable a more productive and organized working environment:


conversational response variants

As you add steps to a story or rule, Jargon both shows you the names of the elements you already have and surfaces key details (such as the text for a response, or a sample utterance for an intent) to help you choose the one that makes the most sense for the scenario at hand. When you do need a new element Jargon makes it quick and easy to provide the new name and then fill in the details when you’re ready.

Sample dialog

conversational response variants

As you view and edit application components Jargon shows you sample dialogs that represent what actual user interactions with the application might look like. For stories and rules these samples help you understand what the story is trying to accomplish. The sample dialogs for intents, responses, and forms make it easy to see how the element is used within your application, and what the impact of making a change might be.


The inspector gives quick access to key information without requiring you to jump to a different location and lose your place. The inspector starts with a categorized overview of all of the elements used in a story (intents, responses, etc.), and provides quick access to critical details such as sample utterances or response components. As you navigate through a story the inspector automatically surfaces those details for the focused element.

Application-wide validation

application-wide validation

Jargon constantly validates all elements of your application to detect and prevent errors. Errors are flagged immediately while editing, and should something slip through the cracks further checks during the release process prevent your application from breaking in production.

Version history

version history

All changes in Jargon are tracked in a version control system, giving you full access to the history of every element and diff views of those changes. If you happen to edit an item that someone else on your team has changed, Jargon will highlight the conflict and guide you through the resolution process.

More to come

This IDE is just a small part of our long-term vision for Jargon. We’d love to hear your feedback on what we’ve built so far – Jargon is free to get started – and what additional problems we can solve for you!

Jonathan, CTO and Co-Founder

Subscribe to Jargon’s monthly newsletter

About Jargon

Jargon enables enterprise teams to build, deliver, and optimize conversational apps built on Rasa, Google Assistant, and Amazon Alexa. Jargon’s IDE (Rasa only) increases developer productivity with powerful shortcuts, built-in error checks, and simulated application output, while keeping the many interconnected app components in sync. With a live connection to a conversational app, Jargon’s CMS enables any team member to publish content changes without needing to retrain and redeploy the application. With Jargon, teams can successfully scale and control a project while preventing errors along the way.

Create a free individual account here; Watch tutorial videos here; Subscribe to Jargon’s monthly newsletter here.