Hark Pro Brings Its AI Browser Agent Directly Into iMessage and RCS

Hark has added iMessage and RCS access to Hark Pro, its personal AI assistant. Users can ask it in a text thread to book appointments, make purchases, and complete actions on authenticated websites without opening the Hark app. The update brings Hark’s cloud browser agent into the default messaging apps people already use.

Existing Hark Pro subscribers can enable the feature by asking the assistant to text them. New users can begin on Hark’s website and continue registration in iMessage, skipping the app installation. Conversations and plan limits carry across the messaging, web, and mobile interfaces.

A browser agent enters the thread

Hark Pro is the company’s first public product. Its underlying computer-use model interprets websites and operates their interfaces, while a cloud service called Handoff executes the task. A computer-use model works with buttons, forms, and menus much as a person would, rather than relying on a site to provide an API.

The Handoff browser agent can navigate multiple sites, sign in, fill forms, and complete transactions. Hark’s web and mobile interfaces show that activity in a small browser window. When a task begins in Messages, Handoff still performs the browser work in the cloud while the conversation carries instructions, status updates, and approval requests.

Credentials and payment details remain in an encrypted vault called Secured by Hark, according to the company’s security overview. Hark says employees cannot access the vault’s contents. The assistant requests confirmation before consequential actions such as submitting a purchase.

Conversation history stays synchronized across Hark’s interfaces. A task started in iMessage or RCS appears in the corresponding Hark Pro thread, allowing the user to review or continue it later from the desktop or mobile app.

The release, line by line

Receiving commands through iMessage or RCS does not give Hark general control over a user’s communications. The messaging integration provides an interface for talking to the assistant; separate permissions govern actions involving other recipients.

Chat threads are becoming agent launchers

Hark joins several assistants designed around familiar messaging interfaces. Arlo, Pally, Poke, and Spear Street’s Instinct use iMessage, SMS, or WhatsApp as primary access points, according to a market comparison. OpenAI also offers one-to-one iMessage or RCS conversations to eligible US Pro users through its messaging access.

iMessage is Apple’s proprietary messaging service, while RCS is a carrier-based standard available across supported Apple and Android devices. Together, the two channels let Hark reach many default messaging clients without requiring a dedicated app installation.

The distribution advantage comes from reducing the steps between a request and the assistant. A user can issue a task from an existing conversation interface, receive an approval prompt there, and return later without managing another inbox. Hark launched as an app-first product in October and is now adopting the message-first access model already used by several competitors.

Funding, pricing, and hardware

Hark was founded in late 2025 by Brett Adcock, who also founded robotics company Figure. The company raised more than $700 million at a $6 billion valuation in May 2026, according to a company profile. Adcock has described Hark’s focus as building a practical interface layer for AI and has said the company plans to release an AI-native hardware device in 2027.

The messaging integration does not change Hark Pro’s pricing. A free tier sits alongside plans costing $20 and $100 per month, with paid tiers primarily increasing computer-use allowances, according to a pricing comparison.

Five systems behind one request

A production-grade messaging agent has to coordinate several systems while keeping the interaction legible inside a line-by-line conversation:

• Identity mapping: The service must connect an iMessage or RCS identity to the correct Hark account without creating an account-takeover path.
• Session state: The agent must preserve browser state while it waits for a reply, including logins, partially completed forms, and expiring checkout sessions.
• Approval controls: Confirmation messages should identify the action, recipient, and amount, then expire after use so an old approval cannot authorize a later task.
• Retry safety: Network failures and duplicate messages require idempotent operations, which prevent a retried request from placing the same order twice.
• Secret handling: Credentials and card details should stay outside message bodies and move only between the vault and the browser runtime.

Browser automation also introduces a latency problem. Hark’s co-founder comments indicate that the company prioritizes result quality even when a task takes longer than a rival’s. A text interface therefore needs clear acknowledgements, progress updates, cancellation controls, and recovery behavior when a website fails or an approval expires.

What Hark still needs to document

• Compatibility: Supported countries, carriers, devices, and operating-system versions, plus the behavior when RCS is unavailable.
• Onboarding: Whether direct account creation will extend from iMessage to RCS.
• Transport security: How Hark handles differences in encryption, metadata, and retention across iMessage and RCS configurations.
• Failure handling: Timeouts, retries, task cancellation, duplicate-message protection, and recovery after interrupted approvals.
• Security evidence: Key-management details, independent audits, retention periods, and account-deletion procedures for stored conversations and credentials.
• Developer access: Hark has not announced an API, SDK, or webhook system for third-party integrations.
• Performance: The company has not published latency, completion-rate, or failure-rate benchmarks for tasks initiated through Messages.

Compatibility tables, latency benchmarks, and failure-recovery documentation would show how reliably Hark’s browser agent performs when users cannot see its browser window.