Other Clients
VS Code is the recommended first-run path, but CodeForge works with other DevContainer clients too.
GitHub Codespaces
Section titled “GitHub Codespaces”- Push your project with
.devcontainer/committed. - Open the repository on GitHub.
- Create a Codespace.
- Let Codespaces build the container from
devcontainer.json.
This avoids local Docker setup entirely.
JetBrains Gateway
Section titled “JetBrains Gateway”- Open JetBrains Gateway, or IntelliJ IDEA / PyCharm with the Dev Containers plugin.
- Choose Dev Containers as the connection type.
- Point it at the project directory containing
.devcontainer/. - Let the IDE build and connect.
DevPod and Similar Clients
Section titled “DevPod and Similar Clients”Any client that respects the Dev Containers specification can use the same setup. The main differences are usually around port forwarding and IDE-specific UX, not CodeForge itself.
Key Difference from VS Code
Section titled “Key Difference from VS Code”VS Code auto-forwards ports. Other clients often do not, so you may need dbr or SSH tunneling to access services.