Skip to main content

Phone Harness integration

Developer tools connector, available on Zeplik

Phone Harness is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Phone Harness and Zeplik can act on your software development for you: Phone Harness provides cloud Android phone sessions for automated lifecycle management, observation, and ADB access. You stay in the conversation while the assistant does the work in Phone Harness directly.

Zeplik exposes 11 read actions and 10 write actions for Phone Harness. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Phone Harness without your consent.

Try Phone Harness on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Phone Harness

Read from Phone Harness (11)

Runs automatically in any conversation.

  • Get account

    Get the connected account's identity, balance, Android profile choices, active-session capacity, and whether a new session can be started.

  • Get adb

    Get the current ADB state for an Android session. Returns exactly a disabled result or the enabled connection endpoint and sensitive unlock credential.

  • Get health

    Check public Phone Harness API-process liveness only. This does not certify phone availability, credits, capacity, video, or successful provisioning.

  • Get owner viewer

    Create a secret, short-lived capability for interactive owner control of a ready session. Embedding is restricted to the configured Phone Harness dashboard origin, not arbitrary third-party origins. Reconnecting does not extend the phone deadline. Return it only for secure handoff to the intended account owner; never log, persist, or publish it.

  • Get recent history

    Return up to 100 finished sessions ordered by creation time descending. Use LIST_HISTORY instead when complete cursor-based traversal is needed.

  • Get session

    Get one session's current lifecycle state, deadline, screen geometry, and ADB details. Use it to poll provisioning; state=error is a terminal startup failure, not success.

  • Get snapshot

    Download the latest still image from a ready Phone Harness session as a file. The image is PNG or JPEG. A no-frame-yet response is retryable after the session is ready and has rendered a frame.

  • Get viewer

    Create a short-lived view-only link for an intended person to watch a live session. Return the link for secure handoff; it grants no interactive owner control and must not be logged or published.

  • List api keys

    List metadata for the connected account's API keys, including hashes, labels, hints, creation times, and revocation times. This action never returns raw bearer keys.

  • List history

    Return one cursor-paginated page of finished-session history in newest-first order, with a next cursor for complete traversal.

  • List sessions

    List all active account sessions, including provisioning, terminal-error, closing, and cleanup-pending entries.

Act in Phone Harness (10)

Runs only after you enable write access.

  • Create api key

    Create an account-wide API bearer key that can manage API keys. The raw key is shown only once; store it securely and never log it.

  • Create session

    Start a temporary or saved Android emulator session and return its admitted session data plus the internally generated idempotency key. If the initial POST has an ambiguous transport failure, this action recovers or safely replays that same keyed request once. A provisioning result is not ready; poll PHONE_HARNESS_GET_SESSION until state is ready or terminal error.

  • Enable adb

    Enable or re-enable ADB access for a ready Android session and return its current connection endpoint and sensitive unlock code. Repeated calls are idempotent.

  • End session

    Request that a Phone Harness session end and billing closure be recorded. A cleanup_pending result is asynchronous and continues to consume capacity; use the durable create receipt to confirm cleanup_complete. Repeating cleanup after the session is gone can return session_not_found; that outcome does not prove release or cleanup, even on a repeated call.

  • Recover create request

    Read the durable receipt for an idempotent session create to resolve an ambiguous create result or confirm asynchronous release cleanup.

  • Reset adb code

    Rotate the ADB unlock code for an Android session, invalidate the previous code, and close all existing ADB connections. Returns sensitive replacement connection details that must be used for subsequent connections.

  • Reset device

    Irreversibly erase and reprovision an assigned iPhone, deleting its apps, accounts, and data. The reset takes a few minutes; poll PHONE_HARNESS_GET_ACCOUNT until the device state is available before starting it again. Phone Harness refuses the reset while a session holds the device.

  • Reset profile

    Irreversibly delete the saved Android profile's apps, logins, and data. The next session using its profile ID starts with a fresh phone. Phone Harness refuses the reset while a live session holds the profile phone.

  • Revoke adb

    Revoke ADB access for an Android session. This changes only ADB access: the phone session remains active and session billing continues unaffected.

  • Revoke api key

    Idempotently revoke an API key by its hash. Identifier existence is not proven by a successful response, and active phone sessions are unaffected. Do not revoke the key used by the current connection if continued Phone Harness access is needed.

How to connect Phone Harness

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Phone Harness immediately.

  2. Connect Phone Harness

    Open Settings and go to Connectors, then press Connect on Phone Harness. You can also connect from the Phone Harness page in the app.

  3. Add your Phone Harness API key

    Paste your Phone Harness API key when prompted. Zeplik stores it securely on the server and starts working with Phone Harness right away.

Frequently asked questions

Can I use Phone Harness with Zeplik?
Yes. Phone Harness is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Phone Harness account inside any conversation.
What can Zeplik do with Phone Harness?
Once connected, Zeplik has 11 read and 10 write actions for Phone Harness. Phone Harness provides cloud Android phone sessions for automated lifecycle management, observation, and ADB access.
How do I connect Phone Harness to Zeplik?
You connect Phone Harness by pasting your own Phone Harness API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in Phone Harness without asking?
No. Zeplik reads from Phone Harness by default. Any action that changes data in Phone Harness requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Phone Harness cost?
Connecting Phone Harness is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related developer tools integrations

More on Zeplik

Connect Phone Harness to your AI assistant

Every model, one chat. Bring Phone Harness into Zeplik and let the assistant do the work.