I Texted Instinct. It Tells My Coding Agent What to Build.

Description and use

The author built a bridge between the phone‑based Instinct assistant and the local OpenCode coding agent, automating task handoff, branch management, and result reporting while keeping PM and developer responsibilities distinct.

Problem

The developer needed a way to turn phone‑based requests into actionable coding tasks without manually transferring information between a personal assistant and a local coding agent.

Outcome

The bridge enables seamless handoff between a phone‑based PM assistant and a local coding agent, automating branch management, session reuse, and result reporting while keeping responsibilities distinct.

Workflow

• Send request to Instinct from phone
• Instinct turns request into a work order and pushes it to the bridge queue
• Bridge daemon on Mac pulls task, checks out a sanitized task branch
• Bridge runs OpenCode (CLI or server) with the task
• Bridge collects output, summary, diffstat, and session ID
• Bridge returns result to Instinct
• Instinct informs user of outcome or further actions

Evidence

I built a bridge between them so I would not have to carry every message from one to the other.

Source

The loop is simple: I send Instinct a request from my phone. Instinct turns it into a work order for a configured repository. The bridge on my Mac receives the task and switches to a task branch. OpenCode works in that repository. The bridge returns the output, branch and session information. Instinct uses that response to tell me what happened or what still needs attention.

Source

The bridge is a Node daemon with a source adapter, a core task loop and an executor adapter.

Source