independent developer · Germany
Native Android workflows, agent runtimes, local-first experiments and developer tooling. I like software that gives the user control and makes the interesting parts visible.
$ focus --now
PRIMARY
AGENTCODI
target Android 10+ / ARM64
runtime native app-server
mode protected workspace
stack Java + C++
✓ build the workflow on the device
Selected work
Current work, experiments and the projects that shaped what I build today.
Codex workflows, native on Android.
A native Android workspace around the Codex app-server: chat, workspace files, approvals, terminal access and packaged development tools on the device. Protected mode uses an Android-specific sandbox path rather than quietly falling back to unrestricted execution.
Android ARM64 compatibility work around Codex, including native binaries and an Android sandbox path built around seccomp + ptrace.
Python + Kivy converter for PDF text layers to EPUB 3, with EPUB metadata editing and Android builds through GitHub Actions.
A small native CLI that checks whether a project holds together: docs, changelog, versioning and code structure, with one compact result.
A local control center experiment combining browser models, OpenAI-compatible APIs, Codex and a permission-based skill system.
About
I started with Python and JavaScript and kept moving closer to the system whenever a project demanded more control. These days that means Android, Java, C++, Rust, native tooling and a frankly unreasonable number of experiments around AI-assisted development.
The common thread is simple: I like understanding where the abstraction ends. If a wrapper gets in the way, I would rather inspect the runtime, build the missing layer and make the boundary explicit.
More notes on GitHub ↗Toolbox
Working principle
“Make the powerful parts visible, keep control with the user, and don’t hide a remote workflow behind a native-looking shell.”
Contact
GitHub is the best place for project-specific issues. For everything else, email works.