Deputy Shell Join Closed Alpha
CLOSED ALPHA

Deputy Shell Closed-Alpha Tester Notice

This notice explains important closed-alpha testing information for Deputy Shell. It is an informational tester notice, not Terms of Service, an EULA, an NDA, a liability waiver, a mandatory acceptance checkbox, a tester-consent database field or an in-app blocking notice.

Join Closed Alpha

Alpha status

Deputy Shell is unfinished alpha software. Crashes, freezes, regressions and incompatible updates are possible.

Data loss is possible. Testers should use non-critical or backed-up projects. Deputy Shell must not be the only copy of an important project.

Deputy Shell currently requires Android 14 or later on a supported 64-bit ARM device.

Local data and device behavior

Deputy Shell stores projects, sessions, credentials, preferences and runtime state in app-private storage on the device.

Clearing Deputy Shell app data or uninstalling Deputy Shell removes app-private projects, sessions, credentials, preferences and runtime state.

Android cloud backup and device-transfer backup are disabled for Deputy Shell app-private data. Do not rely on Android backup or device transfer to preserve Deputy Shell projects, sessions, credentials, preferences or runtime state.

Exported copies outside Deputy Shell app-private storage are not deleted automatically when app data is cleared or the app is uninstalled. Review where you save or share exported files.

Runtime setup

The first setup requires a substantial runtime download and extracted storage. Setup and recovery may take time, especially on slower networks or devices with limited available storage.

Runtime-integrity verification protects shipped immutable runtime files from persistent modification and triggers verified reprovisioning when protected files are missing, modified, symlinked, the wrong type or otherwise unexpected. Runtime-integrity verification does not make arbitrary commands, dependencies, packages or agent actions safe.

Terminal, tools, network and credentials

Deputy Shell is a general-purpose terminal and development workspace. Terminal commands can modify or delete files.

Commands, scripts, dependencies and agents may access the network. Third-party tools may transmit source code, prompts, files, credentials or metadata when instructed or required for operation.

Use revocable, limited-scope or testing credentials where possible. Employer-confidential projects, production secrets and irreplaceable data should not be used during early alpha.

OpenAI, Git providers, package registries and other services apply their own terms, privacy rules, limits and charges. Deputy Shell does not provide OpenAI accounts, subscriptions, credits, API keys or hosted AI usage.

Optional Codex use requires your own eligible OpenAI account or supported API key.

Projects and sessions are organizational boundaries inside Deputy Shell. They are not separate Android security sandboxes. Code executed inside Deputy Shell may operate within Deputy Shell's app-private process and storage boundary, including credentials or files available within that boundary.

Rooted devices, modified operating systems, debugging environments and repackaged builds may weaken platform and application protections.

Exports, diagnostics and telemetry

Workspace ZIP export exclusions reduce accidental disclosure but cannot guarantee that every secret is detected. Review ZIP files before sharing them.

Diagnostic exports are intended to support troubleshooting and exclude known high-risk private material where the implementation can identify it. Review diagnostics before sharing them. Do not send passwords, API keys, access tokens, private keys, authentication files, confidential source code, full private repositories or complete private workspace archives unless a separate safe handling process has been agreed.

Firebase Crashlytics and Analytics remain optional and controlled through existing in-app choices.

Closed-test participation

Private Google Play tester links, invitation emails, credentials and non-public builds must not be redistributed.

Invited testers should remain opted into the Google Play closed test for the requested continuous testing period so the closed test can collect meaningful install and retention evidence.

Contact routes