posit-dev / posit-dev/positron
Environment setup stuck at "extension not available" after trusting workspace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
System details:
Positron and OS details:
Positron Version: 2026.10.0 build 70
Code - OSS Version: 1.134.0
Commit: 0b26f1687a50d5406b8ffb81eb2e6bf81906444f
Date: 2026-09-17T17:28:04-07:00
Electron: 42.8.1
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
OS: Darwin arm64 25.6.0
Steps to reproduce the issue:
Open an untrusted workspace. As you might expect, the environment setup can't run in this environment.
However, after trusting the workspace, the "environment setup" feature doesn't engage, even though the extensions do in fact come online and sessions can be started as usual.
Expected or desired behavior:
Environment setup should update after trusting the workspace.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by opening an untrusted workspace, observing that environment setup cannot run, and then trusting the workspace. Trace the environment setup state transition after trust and compare it with the extensions and session state shown in the report. Done means environment setup updates and becomes available after the workspace is trusted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100