Support
General questions and install troubleshooting for Otaconskeep Lite, AI9, and Otacon Expansion. If your question isn't here, ask in Discord: that's the fastest path to Antonio directly.
General
Otaconskeep Lite (built on Otacon Core) is the free, open-source, self-hosted foundation: persistent agents, memory, voice, one command to install. Otacon Expansion is a free layer on top: a five-agent Lite roster with real hierarchy, a live mood/relationship engine, and command-center surfaces (Dashboard, Codec, War Room, Video Studio shells, and more). The Keep is Antonio's own private reference environment: a larger 16+ agent canon plus media automation, smart-home integration, and multi-node GPU orchestration that go beyond what's shipped publicly. Lite installs the foundation. Expansion is the specified public product; the Keep remains the private depth reference, not a downloadable clone.
Otaconskeep Lite has no license key, no time limit, and no artificial feature gate, today or ever. It's the real, complete public platform. KeepRoute, AI9, Expansion, and Keep Desk are all free too, no license key, no seat, no gate. Every model and integration runs locally.
No. Lite, AI9, and Expansion's foundation layer all run entirely on your own hardware with local models. Nothing authenticates against Antonio's own accounts or infrastructure. Optional integrations (Discord, Home Assistant) use credentials you generate yourself and store on your own machine.
Lite runs on CPU alone (a smaller model is picked automatically under 6GB VRAM) up through a 16GB+ GPU for the larger default model. AI9 and Expansion's future Video Studio need an NVIDIA GPU: AI9 supports RTX 30/40/50-series today. There's no minimum GPU for Lite or for today's Expansion foundation install.
Troubleshooting
Normal, not a failure. Click More info, then Run anyway. This happens because the installer is a new/uncommon file to Windows, not because anything is wrong with it.
Expected. Click Yes. A new Setup window opening is normal: the old window can stay open, or it'll say setup continues in the new one.
Normal while Windows enables Linux (WSL2) and Otacon installs. Don't close the window. This is genuinely the longest step.
No. Save your work, restart, and Setup should show WELCOME BACK and continue on its own. If it doesn't relaunch automatically, double-click the same OtaconsKeep-Setup.bat again: it resumes, it doesn't start over.
That's Windows itself, not Otacon: it's finishing the Linux/WSL feature install it just enabled, using the same screen it uses for regular OS updates. This can take 15–45+ minutes, longer on a hard drive than an SSD. If a drive activity light is flickering, it's working. Only treat it as stuck after several hours with zero drive activity: hard power off, reboot, run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth as admin, confirm a few GB of free disk space, then re-run OtaconsKeep-Setup.bat: it resumes rather than starting over.
Windows is creating OtaconsKeep's local WSL Linux environment. Pick any username and a password you'll remember: it's local to your machine only.
Don't open it until the setup window says OTACON IS READY. Opening early looks broken even when the install is completely fine: it's just not finished starting yet.
That's a recovery screen, not a crash. Press R to retry, O to view logs, or X to exit. The window stays open either way.
Re-run OtaconsKeep-Setup.bat (or install_otacon.sh on Linux): it re-checks everything and continues from where you left off without wiping data. Windows status check: OtaconsKeep-Setup.bat --status. Linux health check: otacon doctor.
Recommended: use the download button on the install page. It provides the Windows-formatted installer as tested. Prefer reviewing code first? View source. If the browser blocks the download, use the GitHub ZIP and run the .bat from the extracted folder: don't Save As on a single raw GitHub .bat (that can corrupt encoding).
Troubleshooting
On Linux/WSL: stop the service (sudo systemctl stop otacon.service if present), then remove the install directory (default ~/otacon-ai-ecosystem) and any leftover Docker containers you started. On Windows, the same folder lives under your WSL home; you can also disable the WSL distro from Windows Features if you no longer need Linux. Exact paths are printed at the end of Setup. Ask in Discord if you want a guided teardown.
The Expansion installer looks for Core at ~/otacon-ai-ecosystem by default. If you installed Lite somewhere else, set OTACON_INSTALL_DIR to that path before running the Expansion installer, e.g.: OTACON_INSTALL_DIR=/your/path bash install_otacon_expansion.sh.
READY (exit 0): the test suite passed and the five-agent roster was generated and validated. DEGRADED (exit 2): the roster was still written, but the test suite didn't fully pass: check the install log. FAILED (exit 1): usually Core wasn't found, or the roster failed schema/hierarchy validation. The script always tells you exactly which stage failed and where the log is.
Open http://127.0.0.1:5757/ after Expansion install / soft-update. Command Deck and Codec ship in the product UI. Soft-update: re-run OtaconsKeep-Setup.bat, or in Ubuntu git -C ~/otacon-ai-ecosystem fetch && git -C ~/otacon-ai-ecosystem reset --hard origin/main then restart otacon.service. Hard-refresh the browser.
Yes. It re-syncs the repo, re-runs the test suite, and regenerates the roster: each agent's original creation timestamp is preserved across reruns, nothing is duplicated.
Engineering
How to read the Engineering pages without mistaking scaffolding for a qualification report.
Verified means a requirement has attached executed test evidence (EVID-*) with a recorded result, not Design Intent and not “looks implemented.” Until then the status stays Verification Pending. The portal does not invent PASS. See VCRM.
Rendered theory (KaTeX state vector, blend/decay, Formula 5) lives under Engineering → Math. Parameter tables and model IDs stay on Behavioral Models. About explains the why; Math is the how.
Because Planned procedures exist before Executed runs. Pending is honesty, not a soft PASS. Columns split Planned vs Executed; ST-003 Blocked + EVID-001 is the pattern. Mock analysis data is labeled MOCK and does not flip Verified.
Lite is the free public Core install. Reference Keep is Antonio’s private depth reference, not a downloadable clone. Safe claim: Lite gives persistent local agents + Codec/Command Center paths documented on install. Unsafe claim: “your install matches the full private Keep.” Boundaries are listed on Engineering Overview.
Open the test ID on Tests (e.g. BVT-001 / BVT-002). Follow the published procedure field when present; if procedure is still “Not yet published,” wait for an EVID pack, teaching MOCK traces under Math are not a substitute for a measured run.
Still stuck?
Discord is the fastest way to reach Antonio directly: screenshots and log files help.