Positron
Positron is a data-science IDE from Posit, built on Code OSS for Python, R, notebooks, data exploration and reproducible analysis workflows.
What Positron is for
Positron brings an editor, language consoles, notebooks, variable views and data inspection into one workspace for Python and R analysis. It is useful when a project moves repeatedly between code, tables, plots and exploratory notes. The application does not include every runtime or package, so the selected Python and R environments remain part of the project setup.
Environment and migration boundaries
Desktop builds cover Windows, macOS and common Linux distributions, with separate CPU architectures and package formats. An IDE session can select a different interpreter from the terminal, and Code OSS compatibility does not guarantee that every VS Code extension behaves the same way. Keep the original environment and lock files while testing a migration.
Reproducible use
Record interpreter paths, package versions and project settings before sharing a notebook. Review workspace trust, task scripts, telemetry and extension permissions when opening an unfamiliar project. Validate dependencies, debugging, plots and notebook outputs on a copy before moving production work.
Maintenance note
This page was reviewed on 2026-08-23 against the catalog metadata, current platform requirements and Elastic License 2.0 note. Package architecture and the included runtime files should be checked after extraction.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Positron to this cloud drive
Baidu Netdisk
Save Positron to this cloud drive
Positron installation and first data-analysis workflow
Install Positron 2026.07.1-5, select a Python or R interpreter and run a small reproducible analysis without replacing an existing environment.
Before you start
- Prepare a supported Windows, macOS or Linux system and confirm the processor architecture.
- Install a supported Python or R runtime separately, then keep a copy of the environment and lock files.
- Back up project code and use a small sample dataset for the first test.
Installation steps
- 01
Choose the matching package
Select the Windows, macOS or Linux package that matches the CPU architecture. A package can install successfully and still fail to launch when the architecture is wrong.
- 02
Install and review first-run settings
Complete the normal system installation, then review workspace trust, telemetry, updates and extension sources before opening an external project.
- 03
Select the project interpreter
Use the interpreter or session selector to choose the intended Python executable or R installation. Verify the displayed path instead of relying on the terminal default.
Quick start
- 01
Create a practice project
Make a separate directory with a small script, notebook and sample data so the first run cannot overwrite the working project.
- 02
Run a small analysis
Load the sample, inspect its shape and types, create one derived value and run the current selection. Confirm that the console uses the expected language.
- 03
Check the data view
Compare the variable view, console output and notebook result, then record the interpreter and package versions for the next session.
Usage tips
- Keep dependencies in a reproducible environment rather than installing everything globally.
- Check publisher and permissions before adding extensions; Code OSS compatibility is not a promise of identical extension behavior.
- When a package fails to install, compare the active session path with the terminal path before changing environments.
Troubleshooting and uninstall
Why does Positron not detect an installed Python or R runtime?
Select the executable manually, confirm its version and compare the IDE session path with the terminal path. The two applications may inherit different environment variables.
Why is a package missing after installation?
The package may have been installed into another environment. Check the active interpreter and package library, then install it once in the environment used by the project.
- Preserve project and environment recordsCommit or back up code, export settings and save the Python, R and extension list before removing the IDE.
- Uninstall and clean optional cachesUse the system application manager. Project files, runtimes and package environments are separate; remove their caches only after confirming they are not reused.
Frequently asked questions
Is Positron mainly for Python or R?
It targets both Python and R data-science workflows, including editors, consoles, notebooks and data viewers. Package compatibility still depends on the selected runtime.
Can Positron replace RStudio or VS Code immediately?
Their extensions, project settings and debugging behavior differ. Test a copied project and keep the original environment until the workflow is verified.
Does Positron include Python and R runtimes?
Treat the runtimes and project dependencies as separate prerequisites. Select and verify the environment used by each session.
What should be checked before redistribution?
Confirm the Elastic License 2.0 terms, package architecture, included dependencies and any extension licenses before sharing a bundled setup.