Kaiju Hub Mobile
Kaiju Hub Mobile is the Pro companion for the desktop app. It does not run projects or AI tools on the phone; it securely controls the paired desktop that owns the files, credentials, terminals, and build processes.
Follow the guides to pair your phone, manage projects and ecosystems, resume AI chats, use voice input, or track builds.
What you need
An active Kaiju Hub Pro plan, a supported iOS or Android device, and an up-to-date desktop app that is signed in and online.
Remote availability
Commands travel through the paired realtime bridge, so the phone and desktop do not need to remain on the same Wi-Fi network.
Desktop is the source of truth
Projects, model availability, API keys, build tools, and deployment credentials remain on the desktop.
Version compatibility
New mobile controls appear only when the paired desktop exposes the matching command. Update both apps if a control is unavailable.
Sign in and pair a desktop
- Sign in to the mobile app with the same Kaiju Hub account used by the desktop.
- On desktop, open Settings → Mobile Devices to see the pairing QR code.
- Open the phone or tablet's pairing scanner and scan the QR code.
- Wait for the desktop to appear online, then open Projects to verify that the bridge is connected.
Pair more phones, tablets, or desktops whenever you need them; adding a device preserves your existing connections. Production pairing uses only QR scanning, with manual codes available in development and test builds. Revoking a device removes only that pairing. If revocation fails because the desktop is temporarily unreachable, the app preserves the connection so you can retry.
Projects and files
Project dashboard
Browse Favorites and All Projects in grid or list form. Current desktop builds can provide 16:9 project thumbnails, tech-stack fallbacks, and live running-state indicators.
Project actions
Touch and hold a card or list row to open Project actions. Choose Move, select a position or use the arrows, then tap OK. The same menu offers favorites, project and folder renaming, group assignment, and copying the desktop path.
Start and stop
Use the project run control to start or stop the paired desktop project and confirm its current state from the project header.
Create projects and ecosystems
Start a single project or choose Ecosystem to create 2–4 connected apps on the desktop. Define the shared objective, coordinator, and each app’s role and framework.
Connect existing projects
In Project actions → Ecosystem connections, select 2–50 existing projects, describe their responsibilities, and tap Save. An unlinked project can join an existing ecosystem with all of its members.
Files and previews
Browse folders, open text files, inspect generated images, and use the development preview when the desktop project exposes one.
Connection recovery
Cached project metadata keeps navigation responsive while the transport reconnects. Mutating actions still require an active paired desktop.
AI chat and voice
Desktop-synced agents
Open project chat tabs for Claude Code, Codex, Gemini CLI, or Grok. Supported models are synchronized from the desktop instead of being fixed to the mobile release.
Reasoning controls
Choose the supported reasoning effort for Claude, Codex, and Grok sessions before sending a prompt.
Past chats and steering
Find sessions for the current project and provider by last activity: Today, Last 7 days, Last 30 days, or a custom day. While work runs, the composer indicates whether a follow-up goes to the active chat or the queue.
Voice input
Choose Phone or Desktop under Settings → Voice → Input. Desktop mode records on the phone and uses the desktop’s configured speech service. Finish recording, wait for transcription, and review the text before sending.
Hands-free assistant
Voice Assistant mode listens for speech, submits after silence, reads responses aloud, and reports progress while the paired desktop agent works.
Media and terminal output
Open generated images and supported attachments from chat, save images to the phone, and inspect terminal output attached to the active session.
Build, Git, and deploy
Git status and sync
Review changed files, commit, push, pull, choose branches, configure auto-sync, and link or unlink a GitHub repository through the desktop.
Build targets
Choose targets supported by the project, including desktop artifacts, website-release APKs, Android production AABs, and other mobile build variants.
Version settings
Read and update the desktop project’s auto-increment preference and major, minor, or patch bump behavior before a build.
Build progress
Open Task Manager → Project builds to inspect stages, output, results, and errors. Use Refresh output for updated details or Stop build to request cancellation. Find finished artifacts in Build versions.
Share build downloads
Use Cloudflare upload to send a local artifact to a linked R2 bucket. Copy a timed download link, then use Extend or Renew link when needed. Share the refreshed URL because old URLs retain their original expiry.
Deployments
Manage the deployment providers currently exposed by mobile: Vercel, Netlify, and WordPress. Provider credentials stay on the desktop.
External effects
Git pushes, builds, uploads, and deployments change external systems. Review the selected project, branch, target, and provider before starting them.
Block Library and Marketing
Block browser
Browse desktop block groups, open component details, inspect source, and preview supported HTML, CSS, JavaScript, JSX, and GLSL content on the phone.
Remote block generation
Run text-based Direct AI or variation generation on the desktop, then apply the result or add a variation back to its component group.
Generation history
Review Direct AI history and component variations. Mobile refreshes the relevant view when the desktop reports that generation completed.
Campaign workspace
Open Marketing campaigns and work with Posts, Brief, Media, Trends, and Rivals from the companion app.
Content workflows
Generate or edit campaign content, attach existing media, research trends and rivals, and use the calendar to organize scheduled posts.
Publishing
Publishing to X is an outward-facing action. Confirm the account, content, media, and schedule before sending.
Settings and security
App lock
Protect the app with a device PIN and supported Face ID or fingerprint authentication. The lock refreshes after the configured inactivity period.
Secure sign-in
OAuth uses the PKCE authorization-code flow. Pairing payloads and device identifiers are validated before credentials are stored.
Encrypted bridge
Current protocol v3 frames are authenticated and encrypted with pairing-derived keys. Nonces and replay checks reject duplicate or stale event frames.
Choose your relay (Pro)
In desktop Settings → Remote Machines → Phone connection, choose Kaiju Hosted, a project in your own Supabase account, or a self-hosted Kaiju Relay. Each desktop has its own choice. Update both apps before switching.
My Supabase setup
Connect your Supabase account once, choose an organization and project, then select Set up and use. Kaiju configures private messaging and tests delivery before switching. Supabase usage and project limits belong to your account; use a dedicated relay project.
Self-hosted setup
Enter your HTTPS domain and save the setup package. Point the domain at your server, install Docker with Compose, then extract the package and run sh start.sh. Return to the desktop and select Test and use. The package configures the relay and HTTPS; you maintain the server.
What stays with Kaiju
Sign-in, Pro checks, pairing and device revocation still use Kaiju. Your chosen relay carries encrypted messages and can see connection addresses, timing and message sizes. Your account tokens and pairing keys are not sent to a custom relay.
Changing providers
Updated phones pick up the desktop’s choice within a minute or when reconnecting. A failed setup keeps the current route. If a selected relay goes offline, Kaiju does not switch providers automatically. Choose Kaiju Hosted in desktop Settings to switch back.
Fail closed
The production bridge does not fall back to plaintext commands when verification fails. A broken pairing must be repaired or recreated.
Synced settings
Tech-stack defaults, media-generation catalog details, and selected build preferences can be read from or written to the paired desktop where supported.
Unpairing
Revoke a phone from the desktop or unpair in mobile settings. Re-pair with a fresh QR code if the trusted relationship should be restored.