Litter

Why it's ranked here

The architecture gives Litter a credible reason to exist beyond a small remote-control shell. Shared state and transport logic reduce behavioral drift between its clients, while native layers retain platform features. The verdict is mixed because development remains active, several voice controls are incomplete, and the repository audit records unresolved dependency advisories.

What's good

One canonical Rust state owner feeds typed snapshots to both native clients. That avoids separate Swift and Kotlin reducers interpreting the same server events differently. The core also centralizes discovery inputs, reconnect policy, hydration, authentication, terminal state, and multiple transports. Fast development lanes and explicit cross-platform acceptance steps support practical iteration.

Tradeoffs

Building from source carries a substantial toolchain: Rust cross-compilation, Xcode, Android SDK and NDK, Java, Zig, generated bindings, patched submodules, and platform packaging. Some behavior still needs physical-device verification. Android speaker routing is unfinished, audio meters lack real telemetry, and arbitrary existing-thread selection for voice handoff lacks an end-to-end typed contract.

How to use it well

Litter suits developers who already run Codex or Local Studio and want to monitor, resume, or operate those sessions away from their main workstation. Use SSH tunneling for remote access, keep working-directory scope aligned when locating sessions, and test audio or networking changes on devices. It does not eliminate host configuration, credentials, mobile build tooling, or release-signing work.

Observed

License

GNU GPL version 3 with additional section 7 permission for Apple App Store and Google Play distribution.

Implementation languages

Shared Rust core with Swift platform code and Kotlin platform code.

User interfaces

Native SwiftUI and Jetpack Compose clients with terminal, session, streaming, and voice surfaces.

Platform support

iOS and Android clients, plus Apple Watch and Mac Catalyst build lanes.

Install and distribution

Apple App Store listing, Android beta distribution, Google Play release tooling, and Mac Catalyst packaging.

Build structure

Make-based orchestration covers Rust checks and tests, generated bindings, native builds, packaging, and release workflows.