Stop copying commands, logs, and files back and forth. OpenSynapse gives an AI client bounded access to an authorized machine, lets it do real work, and checks the result.
AI can already explain what to do. The frustrating part is still you moving commands, error logs, files, and machine state between the chat and the place where work actually happens.
Ask for the outcome. The authorized node performs bounded work instead of handing the terminal back to you.
“Done” is not enough. Meaningful actions should finish with an observable check when the target can be verified.
Server first. Desktop and Android nodes follow the same public interaction model while remaining independent runtimes.
This is an early usable base, not a claim that the whole vision is finished.
git clone https://github.com/nslabhwan/ns-agent-reliability.git
cd ns-agent-reliability
OPENSYNAPSE_ROOT=/srv/my-app bash install.sh
opensynapse doctor
# Optional OpenAI Secure MCP Tunnel prepare path
opensynapse connect openai \
--tunnel-id tunnel_REPLACE_ME \
--prepare-only
Linux one-install bootstrap
Android/Termux fresh install on real device
Bounded MCP read / write / commands
Android stdlib MCP write + readback E2E
Real ChatGPT Secure MCP Tunnel write + readback E2E
59/59 regressions
Reduce the remaining one-time account-side setup
Portable Android media/device modules
Multi-device pairing and routing
Desktop packaging and resumable jobs
The target is not another dashboard. It is the AI interface you already use gaining a safe path to real work.
Inspect allowed files, run bounded commands, make the permitted change, then verify the test result.
Android itself becomes an independent work node. Android/Termux is now a verified public node. Media and device-control modules are the next Android expansion.
Long-running resume and continuity are planned around the same verified-result principle.
Machine access is a trust problem, so safety has to be visible to the user rather than hidden in architecture diagrams.
The current local HTTP endpoint binds to loopback by default. Do not expose an unauthenticated local endpoint directly to the public Internet.
Try the Linux Alpha on a disposable or non-critical workspace. Tell us where installation, trust, permissions, or the first real task feels confusing. Do not include secrets in public issues.