Documentation
The Darkian Studio docs cover installing, using, and troubleshooting DS, plus how its runtime bridge works and how it compares to VS Code, Acode, and Roxum.
Darkian Studio (DS) is a real, mobile-first IDE for Android and Linux. Editor, terminal, LSP, debugging, git, AI chat, and local offline AI models all run against one runtime reached over a bridge. Start with install, then take the getting-started tour.
Get set up
- Install — install Termux, download the beta APK, run one setup command, verify.
- Getting started — a first-run tour: open a project, use the terminal, edit with LSP, debug, and run git.
Understand it
- Architecture — how one runtime serves the editor, terminal, LSP, debugger, git, and extensions over a bridge.
- AI features — the chat agent, local GGUF models run fully offline, inline completions, and MCP.
- GitHub workspaces — open a repository on GitHub without cloning it: sign in, pick a branch, and edit and commit straight against it.
- dsterm — the open-source Rust runtime bridge DS connects to: PTY, LSP/DAP/MCP/extension-host bridges, and command execution.
Fix it
- Troubleshooting — diagnostics logs, crash reports, what to include in a bug report, and known limitations.
Compare it
- DS vs VS Code — mobile-first runtime bridge versus a desktop-first editor with the full
vscodeAPI. - DS vs Acode — one shared runtime for everything versus a mobile editor with a focused PTY/LSP backend.
- DS vs Roxum — a bridge-runtime IDE with DAP/debugging and Open VS X extensions versus a native-Rust-editor Android IDE with on-device AI.
Also useful
- FAQ — direct answers to the most common questions.
- Changelog — what shipped in each release.
- GitHub Releases · Report a bug · Discussions