Positron: Posit's data science IDE, built on Code OSS for R and Python together

Three bullet points, one positioning

The project describes itself in three lines, a next-generation data science IDE built by Posit PBC, an extensible polyglot tool for writing code and exploring data, and a familiar environment for reproducible authoring and publishing. Each line is a positioning decision, next-generation against the incumbent RStudio that Posit also maintains, polyglot against the single-language tradition of R IDEs, and familiar for reproducible authoring pointing at the quarto and notebook workflows the data science world standardized on. Posit PBC, formerly RStudio the company, is the maker, and the IDE inherits the company's two decade understanding of how data scientists actually work rather than starting from a text editor's assumptions.

Code OSS underneath, with its documentation

Positron is built on Code OSS, the open source core of Visual Studio Code, and the documentation strategy follows from that, to learn about basic features like commands, settings, using source control and more, see the VS Code documentation, because they are literally the same features. The repository's package.json confirms the depth of the fork, named code-oss-dev at version 1.134.0 with a distro commit pinned, the upstream workspace structure intact with extensions, remote, src and build directories, and the product label set to positron. The consequence for users is concrete, every VS Code tutorial about keybindings, profiles and settings sync applies, and the learning curve for the editor half of the IDE is zero for anyone who has used VS Code before.

An AI layer in the tree

The repository carries an ai-lib directory as a workspace, and the build script compiles three of its packages, ai-config, ai-credentials and ai-provider-bridge, a structure that names the architecture of the IDE's assistant features, configuration separate from credential storage separate from provider integration, with a compile-copilot target in the build pipeline alongside compile-client. The search interest around the product confirms the direction, questions about using Claude, Codex and Copilot inside Positron are common, and the e2e test environment files include an agent host with its own end to end coverage scripts, suggesting the AI surface is tested like a product feature rather than bolted on. For teams evaluating AI-assisted data science tools, the provider bridge design implies multiple backends rather than a single vendor lock.

A monthly release train

The release cadence is calendar versioned and brisk, 2026.08.2-4 on August 21, 2026.09.0-256 on September 3 and 2026.09.1-2 on September 4, three releases inside three weeks, each tag encoding year, month and a build sequence. Producing builds from a continuous integration system for macOS, Windows and Linux desktop is stated as the current installation path, with downloads from the website rather than through package managers, and the repository pushed the day before this writing. For a desktop IDE in active development, that rhythm signals both momentum and churn, new features arrive monthly and so do behavior changes, so teams standardizing on it should pin a version and upgrade deliberately rather than riding each tag.

Elastic License 2.0, deliberately

The licensing is stated with unusual directness, Positron is licensed under the Elastic License 2.0, a source-available license, with a dedicated page explaining what the license means and the decision to use it, and the trademark line, Positron and the Positron icon are trademarks of Posit Software, PBC, all rights reserved, completes the commercial posture. Elastic License 2.0 permits use and modification but restricts providing the software as a managed service, the standard reason companies choose it, protecting an IDE business from someone else hosting Positron as a product. GitHub reports the license as unclassified, a side effect of ELv2 not being an OSI license, and anyone redistributing or embedding the IDE should read the license text rather than assuming open source terms.

The contributor apparatus of a serious fork

The repository root shows what maintaining a Code OSS fork entails, rebuild scripts for the platform builds, a gulpfile driving the compile pipeline, product.json and cgmanifest.json tracking the dependency provenance, CodeQL configuration for security scanning, ThirdPartyNotices and a NOTICE file, plus a cli, docker, jenkins and remote directories alongside the expected src and extensions. The testing surface is layered, node and browser unit tests, vscode-test for extensions, vitest for Positron-specific code, and Playwright end to end suites with dedicated environment files, including the agent host e2e coverage mentioned above. A .mention-bot, git blame ignore revisions and an agents configuration round out the modern maintenance tooling, and a code of conduct and security policy complete the governance file set.

Feedback through Discussions, docs on the site

The feedback loop is explicit, join GitHub Discussions to ask questions and share feedback, with a feedback page on the website covering how to give feedback and report bugs, the separation keeping the issue tracker for defects while Discussions absorbs the usage questions an IDE attracts. The website carries the before-you-install guidance, the download page, troubleshooting and an FAQ covering common or expected questions, so the README stays short by pointing at each surface rather than duplicating it. For data scientists weighing the switch, the practical onboarding path is the website first, the IDE second, and the VS Code documentation third, in that order, since the first two are Positron-specific and the third covers everything inherited.

Editorial conclusion

Try Positron when your work spans R and Python plus notebooks and data exploration and you want VS Code's editor mechanics underneath a data-science-first shell, since the Code OSS base means familiar commands, settings and source control carry over directly. Stay with RStudio or plain VS Code when extension ecosystems or specific workflows bind you there, and verify the Elastic License 2.0 terms against your use case, since source available is not open source. Before adopting, read the website's before-you-install guidance and FAQ, expect a fast release train with builds like 2026.09.1-2, and take questions to GitHub Discussions, which the project runs as its feedback channel.

Frequently asked questions

Official sources

1. Issues
2. posit-dev/positron on GitHub
3. Project website
4. README
5. Releases