TermFold Debian Coding Terminal
Run Debian projects and popular AI coding agents on an Android phone or tablet.
- Source repo
- Bibarud/TermFold
- Stars
- ★ 15
- Last updated
- 18d ago
- License
- Apache-2.0
- Primary language
- Kotlin
- FA score
- 51/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- Developers with an Android tablet and keyboard who want git, Python, or Node.js in Debian projects.
- Not a fit if
- Users who need systemd, kernel modules, or raw sockets
- Users on devices other than arm64 or x86_64
- Users who cannot keep projects in app storage
- Source review
- 51/100 · Major gaps
What does this agent do, and when should you use it?
TermFold is an Android 8.0+ app that runs a Debian 13 userspace with PRoot in app storage, without root. Its Kotlin and Jetpack Compose interface connects the Termux terminal emulator to a real PTY. In project directories, users can run bash, apt, git, Python, Node.js, and tools such as Claude Code, Codex, Gemini CLI, OpenCode, Cursor, and Pi; ACP-speaking agents can also use a native chat UI over JSON-RPC on stdio. The app includes a file manager, code editor, and browser, and can expose browser MCP tools to agents. Projects live in Debian's ~/projects directory; the app is installed from GitHub APK releases, and uninstalling or clearing app data deletes the Debian environment and projects.
On the first Shell launch, TermFold sets up a Debian development environment with updates, build tools, git, Python, and Node 22. Users can start an empty project, clone a Git repository, or import a device folder, then launch a shell or command-line agent in that project; an agent installs itself the first time its command is entered. Alternatively, users can create an ACP session, where the app communicates with the agent over stdio using JSON-RPC and renders Markdown replies, tool calls, plans, permission prompts, and model, reasoning, and mode controls. The built-in file manager can browse, search, edit, and manage files. The browser previews development servers or websites, and agents can use MCP tools or the termfold-browser command to read pages, click, type, scroll, take screenshots, and inspect the console. Users can import, export, or share files, and check for app updates that are downloaded, verified, and handed to Android's installer.
- Developers with an Android tablet and keyboard who want git, Python, or Node.js in Debian projects.
- Individual developers who want to run Claude Code, Codex, Gemini CLI, OpenCode, or Pi from an Android terminal.
- Developers who want an ACP agent in a native chat UI with visible tool calls and permission prompts.
- Tablet users who need to browse project files, edit code, and preview a local development server side by side.
- Users who want to clone a Git repository or import device files into a Linux project directory.
How do you install or deploy this agent?
Download and install the APK from the latest GitHub release. The device must run Android 8.0+ on arm64 or x86_64 and have a few GB of free space. The first Shell launch downloads a few hundred MB and sets up the Debian development environment. You can also add the repository to Obtainium for release updates.
How do you use this agent?
After installing the APK, open TermFold and tap “+” to create an empty project, clone from Git, or import a device folder. Open Shell and wait for the initial Debian setup, then run an agent command in the project; the first invocation installs the corresponding tool. To use ACP, create an ACP session in the app. Sign in to the agent in a Shell first; ACP chat reuses that sign-in. Common terminal commands include:
claude
codex
gemini
opencode
piWhat are this agent's strengths and limitations?
- Combines Debian 13, PRoot, and a real PTY terminal in an Android app without root.
- Projects live in Linux storage, where symlinks, permissions, executables, git, npm, and virtualenvs work.
- Supports multiple command-line agents and provides ACP agents with native chat and browser MCP tools.
- Includes a file manager, CodeMirror editor, and browser for users and agents.
- Requires Android 8.0+ on an arm64 or x86_64 device; it does not provide CPU emulation.
- It is not a VM and does not support systemd, kernel modules, or raw sockets.
- Uninstalling the app or clearing its data deletes the Debian environment and projects; export or push a copy first.
- Initial setup downloads a few hundred MB; the README does not specify the costs of individual agents or model services.
How does this agent compare with similar options?
The README compares TermFold with Termux and with combining a terminal app and proot scripts on Android: TermFold brings Debian, a terminal, project management, and agent interfaces into one app. It also notes that Termux uses a similar older Android target version for distribution.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| TermFold Debian Coding Terminal This agent | 51 · Major gaps | Desktop appFree + model costs | ★ 15 | 18d ago | Kotlin | Codex · Claude Code |
| Eleven Reverse Engineering Workbench | 58 · Major gaps | Desktop appFree | ★ 789 | today | TypeScript | Codex · Claude Code |
| Oh My Pi | 54 · Major gaps | CLIFree + model costs | ★ 36k | today | TypeScript | Codex · OpenAI API · Claude API |
| Open Interpreter | 45 · Major gaps | CLIFree + model costs | ★ 69k | 9d ago | Rust | Codex |
How does FollowAgents rate this agent?
Why each dimension lost points
README states no root, no Termux, no account, everything runs in-app, PRoot is a userspace chroot — a reasonable least-privilege design, so least_privilege = 2; but no Android permission manifest or code-level evidence is provided, hence the deduction. User confirmation: ACP permission prompts, browser hand-back, SHA-256 and signature verification before updates are mentioned, giving 2; but no confirmation flow for risky operations (apt install, project deletion) is described. Data-flow transparency only describes architecture (JSON-RPC over stdio, PRoot) without stating where data goes, telemetry, or network behavior — 1. Sensitive data handling notes hidden files such as agent sign-ins are not exposed to the file picker, but no encryption or storage details — 1. Dependency security cites third-party notices and SHA-256 verification but no version pinning or vulnerability scanning — 1. External effects: updates download and hand off to Android installer, an external side effect, but no rollback or failure-recovery detail — 1. Rollback only covers the Ubuntu→Debian migration being resumable and deferrable for a day, no general rollback — 1. Source attribution has THIRD_PARTY_NOTICES and Apache-2.0 — 2.
Self-consistency: architecture diagram, install steps, build commands and limits are mutually consistent — 2. Dependency availability: build depends on py scripts, gradle, ziglang, npm, but no version pinning or checksums — 1. Failure messages: only migration interruption resumability is mentioned; update verification failure behavior is unspecified — 1.
Audience and scenarios: README targets Android tablet/phone developers with detailed scenarios (terminal, ACP chat, browser, file manager) — 3. Capability boundaries: architecture limits, not-a-VM, no systemd, uninstall deletes data are listed — 2; but specific agent compatibility versions are not stated. Trigger precision: ACP sessions, browser MCP tools, shell command triggers are described loosely — 1. Environment fit: Android 8.0+, arm64/x86_64, several GB free space are clearly stated — 2.
Information architecture: README is well-structured with Why/Install/How it works/Building/Limits sections — 2. Install notes: complete steps including Obtainium and build commands — 2. Naming stability: no version number or API stability commitment — 1. Examples and FAQ: screenshots and demo video exist, but no FAQ section — 1. Known limitations: explicit Limits section — 2. License: full Apache-2.0 text — 3. Versioning/changelog: only a 2.2 migration mention, no CHANGELOG — 1. Maintenance responsibility: Contributing section exists, but publisher identity is unverified — 1.
Output usability: rich output forms (terminal, chat, file manager, browser) — 2. Marginal value: provides full Debian and multi-agent support on Android, clear value — 2. Cost-benefit: requires hundreds of MB download and several GB space, and uninstall loses data, high cost — 1.
Claim traceability: many README claims but few links to code or tests — 1. Cross-source corroboration: only README and LICENSE, no test or CI evidence — 1. Fact/inference separation: README mixes factual description with marketing language without clear separation — 1.
- Publisher identity is unverified; update source and signing key should be independently confirmed.
- Uninstalling or clearing data deletes the Debian environment and projects; push to git or export first.
- Update download/install relies on GitHub and the Android installer; failure-recovery details are unspecified.
- Dependencies are not version-pinned, so build reproducibility is uncertain.