Portable Kick-Ass Control Centre
Kick-Ass V6 — original interactive 3D model from this USB
Local browser interface at 127.0.0.1:11477. No VPS connection or autonomous agent tool permissions.
Type commands for tools, diagnostics, or Kick-Ass views. Run invokes only existing restricted checks. The AI chat box is just below this station and remains separate.
Loading approved console commands…
Not CMD, PowerShell, or an unrestricted Kali shell. No automatic AI tool grants; unimplemented catalogue tools are refused.
Local Gemma chat, the original Kick-Ass V6 3D robot, media engines and real restricted checks. Built to travel with the USB, not rely on the VPS. AI chat currently requires a fresh generation retest; Kali physical boot remains unverified.
A larger immersive 3D view of your existing approved model. Drag to rotate, zoom with the mouse or touch controls, and open the full-window viewer when you need more space.
Two operating modes on the same USB. You are viewing the Windows-hosted dashboard. A browser button cannot boot an operating system or create a Kali shell.
Open the USB in Windows and double-click START_RBMCC_MASTER_AI_WINDOWS.cmd to launch local Gemma chat and Kick-Ass.
For real Windows CMD commands, double-click OPEN_NATIVE_WINDOWS_TERMINAL.cmd on the USB. The console runs locally under your Windows account, not on your phone or inside AI Chat.
Physical Kali boot has not yet been verified. To start Kali on this computer:
05_CHECK_KALI_NATIVE_AI.sh, then OPEN_KALI_MASTER_AI.sh.127.0.0.1:18078 in Kali itself.Open the Kali desktop's Terminal app for a real Linux shell. sudo works only with the permissions of your signed-in Linux account. You can also run OPEN_NATIVE_KALI_TERMINAL.sh manually.
Kick-Ass 3D, AI Chat, the 159-tool catalogue and the 16 manually triggered restricted checks are available through the private Windows dashboard.
Not yet available: a streamed Kali desktop, live Kali graphical terminal or arbitrary Linux shell commands from the phone. Those require an actually running Kali machine and separate authenticated remote-desktop or terminal access, not a browser shortcut.
Don't open 127.0.0.1:18078 on your phone: localhost on the phone refers to the phone, not Kali on the PC.
Windows x64 runtimes physically stored on this USB; tools do not acquire AI agent access automatically.
USB engine checksum, version launch and real WAV audio generation passed. To use it, open the USB folder in Windows Explorer and double-click OPEN_FFMPEG_TERMINAL_WINDOWS.cmd.
The Blender executable checksum, USB startup and a real saved .blend project have passed. To use it, open the USB folder in Windows Explorer and double-click OPEN_BLENDER_WINDOWS.cmd.
Restricted, user-clicked read-only checks with actual local handlers. Choose an agent registry identity and press Run yourself. This is an informational mapping, not an authenticated agent login or autonomous permission.
Choose a tool, then press Run read-only check.
Audited directly from the USB catalogue. A previous PC test is not permission to execute on someone else's computer.
FFmpeg and Blender have passed separate Windows USB runtime tests; they are available through their local launcher files, not as unrestricted AI actions. Native Linux Gemma already passed a real Ubuntu runtime test. Physical Kali Live boot and independent second-PC tests remain pending.
Download the 159-tool readiness report Read audit summary
16/159 working manually triggered read-only handlers; 143/159 registered tools still lack USB executors. No authenticated agent identities or autonomous tool grants.
Download current 159-tool implementation matrix Read next-steps roadmap
Tool permissions remain ungranted while dependencies, hardware and approval controls are checked.
Search, compare capabilities and review actual verification state. Tool listing does not confer access.
Select an entry to inspect its available platforms and approval requirements.
53 canonical identities, not 53 independently verified running model workers.
Offline catalogue-aware assistant. This is a deterministic lookup helper — not an LLM and not an autonomous tool executor.
Try: What tools do you have? Or: Find tools for Blender and video.
Host scanning requires your explicit action. No hardware information is automatically collected or transmitted.
Windows: SCAN_WINDOWS.cmd (requires Python 3). Linux: run sh scan_linux.sh. Output stays in USB reports/host_scan.json.
Android: open index.html through a supported USB-OTG file browser. Hardware scanning and local Linux execution require a future companion app, appropriate APIs and user permissions.
A future authenticated integration for other AI systems.
api-contract.json documents proposed read-only discovery and permission-checked execution interfaces. No remote USB API server is enabled, and no incoming external AI tool grants exist.
Planned: tool discovery → eligible agent and platform selection → explicit approval → bounded execution → receipt and rollback evidence.
Owner-only server, private tunnels, credentials and remote access are intentionally excluded from a sharable USB.