Skip to content

App method (exploratory): read desktop-app agent sessions, piloting with Cursor #20

Description

@deehw

Method: App (exploratory) · Priority: P2

Harness has two shipping integration methods — CLI (engine: we read the transcript your agent already writes) and API (provider: you host an HTTP endpoint). Some agents live in neither: their sessions exist only inside a desktop app (see ZCode #16, MiniMax Code #17).

We're exploring a third method for exactly that shape: App — a companion process on the host machine reads a desktop agent app's session state and emits the same normalized event stream engines produce. The pilot target is the Cursor desktop app: Harness already drives Cursor's CLI agent, but IDE-side agent sessions are invisible to it today.

This issue tracks the pilot: whether the app's session state is readable on stable terms, whether the mapping onto the normalized lifecycle (ready · listening · working · waiting · done · error) holds, and — if it does — what the method's contract looks like for other desktop apps. If the pilot fails on stability, the method stays experimental and this issue says why.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Next wave — community first; first-party if unclaimedintegrationA new agent integrationmethod:appApp path (exploratory) — session state read from a desktop agent app

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions