Build on DEVAE, not just in it
A CLI, a VS Code extension and the same JSON API our own apps run on. SDKs and webhooks are on the way.
What you can build with today
CLI
Log in, open rooms, share your screen and terminal, and ship — all from the command line. macOS, Windows (PowerShell) and Linux.
AvailableOpen →VS Code extension
Host or join a collaboration session from the Command Palette. Installed from a .vsix during the beta.
BetaOpen →REST API
The same JSON API the web, desktop and Android apps use: profiles, posts, snippets, rooms. Token auth via the CLI login flow.
BetaOpen →Webhooks & SDKs
Event delivery and typed client libraries are on the roadmap. Tell us what you would build with them on the feed.
PlannedOpen →Three commands to a live room
# Install the DEVAE CLI $ npm i -g @devae/cli ✓ linked devae command # Authenticate $ devae login ✓ authenticated as @you # Join a room, share screen + terminal $ devae room join refactor-payments ● live · 3 collaborators
Works where you already work
The CLI wraps the same room, screen-share and terminal-share features as the desktop app. No plugins, no setup calls.
- yarn / pnpm / bun — use whichever package manager you like.
- GitHub OAuth — sign in with the account your repos live on.
- Run engine — run code in the room in multiple languages.
Questions, answered
The API is in beta. Endpoints used by our own clients are stable enough to build against, but there is no versioning guarantee yet. Breaking changes are announced in the newsroom.
Run `devae login` in the CLI or sign in on the web; both issue a bearer token you can reuse for API requests.
Yes — public profiles and posts are linkable and unfurl with rich previews, and the "Find me on DEVAE" README badge is at /tools/readme-profile-generator.
Full reference docs are being written alongside the beta. Until then this page, the CLI `--help` output and the community are the best sources.
