Skip to content

Known-Limitations.md

Latest commit

 

History

History
71 lines (46 loc) · 1.88 KB

Known-Limitations.md

File metadata and controls

71 lines (46 loc) · 1.88 KB
Raw

Known Limitations

This page sets expectations for the current Coder Studio release.

What This Page Solves

Coder Studio is easiest to understand when its boundaries are explicit. It is not a cloud IDE, not a VS Code replacement, and not an AI model provider.

System Requirements

  • Node.js 24 or newer is required.
  • Coder Studio is installed as a global npm package.
  • Agent sessions depend on local Provider CLIs installed on your machine.

Provider Boundary

Coder Studio does not bundle Claude, Codex, or other models. It launches and manages local Provider CLIs inside the workspace.

Without a Provider CLI installed, you can:

  • open a workspace
  • browse files
  • use terminals

You cannot create that provider's agent session until the CLI is installed and visible in PATH.

Mobile Boundary

Mobile is best for monitoring and review, not heavy editing.

Good mobile use cases:

  • check long-running task progress
  • read agent output
  • browse files
  • inspect Git diffs
  • decide whether desktop intervention is needed

Remote Access Boundary

Coder Studio is safest on localhost or trusted networks. Cross-device and public access require your own network and authentication setup.

Before remote access:

coder-studio config --password <strong-password>
coder-studio config --host 0.0.0.0
coder-studio serve --restart

Do not expose Coder Studio to the public internet without authentication.

Not The Focus Of This Launch

The current launch does not focus on:

  • hosted cloud workspaces
  • team permission systems
  • phone-first full coding
  • plugin marketplace
  • session replay
  • cloud preference sync

These may evolve later, but they are not required to understand the first Coder Studio workflow.

Next Steps