Replace Aight?
KINDA ยท weekend projectA focused multi-backend iPhone prototype is a realistic multi-day build when a local companion normalizes each agent protocol, but hardening all four adapters plus Aight's hosted relay, voice, orchestration, sync, and App Store polish is multi-week product work.
Build me a local-first iPhone client for Codex, Claude Code, OpenClaw, and Hermes. Requirements: - Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone. - Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose start, resume, prompt, event, approval, interrupt, and capability operations; session listing is optional and capability-gated. - Ship real adapters for all four. Disable unavailable agents at runtime; all adapters must compile and pass fixture tests without every agent installed. - Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise app-server over stdio using the generated v2 types. - Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs, async-iterable input for interrupt(), and canUseTool for permissions. - OpenClaw: use the official Gateway WebSocket client, pair once, request only read/write/approvals/questions scopes, and store its device token securely. - Hermes: use /v1/runs and its event, approval, and stop endpoints; use session headers for continuity and discover features from /v1/capabilities. - Keep backend models in the companion and expose one versioned protocol. The iOS app stores its wss:// endpoint and bridge bearer token in Keychain. - Provide backend/session pickers, streamed Markdown and tool events, approval cards, Stop, capability-aware controls, and deny approvals on disconnect. - Bind to 127.0.0.1 and compare the random `.env` token in constant time; expose it only through private Tailscale Serve HTTPS, and never enable Funnel. - Add bounded reconnects and local completion notifications. No app accounts, cloud database, analytics, or telemetry; agent model-provider calls remain. - Out of scope: hosted relay, voice, cross-backend groups, templates, community skills, themes, multi-device sync, and a macOS client. - Test adapter fixtures plus denial, interruption, and reconnection. README: setup for all four, `.env.example`, Tailscale, signing, permissions, limits.
$ open in your agent (prompt prefilled, you press enter) or copy it raw
They pay for one polished client that safely reaches several agent backends from anywhere, keeps sessions in sync, and handles notifications, voice, and approvals without maintaining a custom mobile integration.
xmanaged encrypted relay and push notifications
xvoice mode with local speech models
xcross-agent teams and group-chat orchestration
xpre-built agent/team templates and community skill browsing
xmulti-device sync and App Store polish
What does the Aight verdict mean?
The core job looks buildable, with meaningful gaps: managed encrypted relay and push notifications, voice mode with local speech models. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for Aight?
The directory records $4.99/month for Pro, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing Aight?
Honestly: managed encrypted relay and push notifications; voice mode with local speech models; cross-agent teams and group-chat orchestration; pre-built agent/team templates and community skill browsing; multi-device sync and App Store polish. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Aight?
The listed prior art includes Happy (Open-source mobile and web client for Codex and Claude Code with end-to-end encryption.), CodexAppMobile (Open-source SwiftUI iOS client for a remote Codex app-server.). Inspect those projects before starting from a blank prompt.