Conversation that continues
Chat, incremental responses, attachments, pinned Mac sessions, cancellation, and a visible send-next queue continue the same Agent rather than starting a second mobile identity.
IPHONE + IPAD
NativeAgent keeps the living runtime on Mac while giving iPhone and iPad a first-class surface for conversation, work, approvals, memory, providers, and living-system status.
MORE THAN A COMPANION
The mobile app does not invent a parallel agent runtime. It reaches the same Mac-owned identity, context, provider policy, tools, Workshop, and trust boundaries through signed coordination.
Chat, incremental responses, attachments, pinned Mac sessions, cancellation, and a visible send-next queue continue the same Agent rather than starting a second mobile identity.
Review approvals, follow Workshop work, inspect activity, and send signed remote actions back to the Mac with durable transaction readback before success is shown.
Memories, skills, connectors, provider status, runtime health, and organism living status arrive through focused snapshots instead of cloning the Mac runtime onto the phone.
Signed iCloud and CloudKit coordination keep the phone connected, while APNS brings meaningful edges—like approvals and work needing you—to the lock screen.
SIGNED CONTINUITY
Mobile actions are signed, routed to the Mac authority, and checked against the same policy that protects local actions. The phone waits for durable response readback before presenting success.
MOBILE, CLEARLY
The Mac app owns the live runtime. iPhone and iPad are native remote surfaces for that same Agent—not separate brains.
Yes. Signed approval and Workshop actions return to the Mac authority and require durable response readback.
Provider and model controls are available through signed coordination, while API keys remain on the Mac.
No. NativeAgent is intentionally an Apple-platform system: a Swift-native Mac runtime with iPhone and iPad continuity.
ONE APPLE-NATIVE SYSTEM