289 — tp overview: interview an idea from its card, in an agent session in the browser (#289)

Why

An idea on the board is a card with a title and nothing to do. To get it going the human opens a terminal in the right repository, starts an agent and tells it which idea to interview. The board is where they see the idea and decide its turn has come, and it is in a browser already.

A spike on 2026-11-16 showed the pieces are there: claude --remote-control NAME PROMPT, given a terminal of its own, starts a session on this machine, in the directory it is run in, takes the prompt as its first message, and prints the address of the session on claude.ai/code. The agent, its commands and its tokens are this machine's; the browser shows the conversation.

This is a first cut, to see how well an interview held that way works.

What changes

  • User config, a forge under overview:: a new key, dir, the directory that holds the checkouts of that owner's repositories; repository NAME is at <dir>/NAME. A leading ~ is the home directory.
  • tp overview, every card in "Ideas": a button, "interview".
  • The button starts claude --remote-control in the repository's checkout, under a terminal of tp's own, with a first message that asks for the interview of idea N, and sends the browser to the session's page on claude.ai/code. It writes nothing to a forge: what the interview ends in (tp issue close, tp idea roadmap, tp idea story) the agent runs, as the human decides.
  • A session lasts while tp overview runs, and ends with it.
  • docs/overview.md.

Acceptance

A card on the board:

Column The page The card
Ideas with its secret the button "interview"
Ideas without its secret no button
any other any no "interview"

Pressing "interview" on the card of idea N of repository NAME. "The session's address" is the first https://claude.ai/code/… that claude prints.

The request The forge of the card <dir>/NAME claude An interview of this idea started by this tp overview Outcome
the page's form of the user config, dir set a directory prints the session's address within 60 seconds none started in <dir>/NAME, named NAME #N, its first message asking for the interview of idea N by number and title; the browser sent to the session's address
the page's form the same the same the same one, still running none started; the browser sent to that session's address
the page's form the same the same the same one, since ended started again, as the first row
the page's form of the user config, no dir — — — nothing started; the page says to set dir, naming the user config's file and the forge
the page's form of the user config, dir set absent, or not a directory — — nothing started; the page names the path
the page's form the same a directory not on the PATH — nothing started; the page says so
the page's form the same a directory ends without printing an address none the page gives the last line it printed
the page's form the same a directory prints no address within 60 seconds none stopped; the page says so, with the last line it printed
the page's form not of the user config — — — refused; nothing started
the page's form, NAME with a / or .. in it any — — — refused; nothing started
without the page's secret, or with another's any — — — refused; nothing started
not a POST any — — — refused; nothing started
under a host name other than this machine's own any — — — refused; nothing started
tp overview Its interviews still running Outcome
stopped (interrupt, or terminate) some each is stopped with it

The first message, for idea N titled TITLE: it names the idea as #N TITLE, asks for it to be interviewed as docs/idea.md of task-plus describes, one question at a time, and names the three ends: closed, tp idea roadmap N, or tp idea story N and the story written and offered.

Out of scope

  • A page of tp's own for the conversation: it is held on claude.ai/code, and needs the account signed in there and claude remote-control allowed once on this machine.
  • "interview" on a roadmap card, whose turn has come.
  • Listing or stopping the running interviews from the board.
  • Checking that <dir>/NAME is a checkout of that repository, is on its base branch, or is up to date.
  • Choosing the session's permission mode or model.
  • Another agent than claude.
  • Windows: a terminal of tp's own is made on Linux and macOS.
  • tp claude (#269): this does not use it.

Decisions

none

Done when

  • tests express the acceptance table and pass
  • spec updated
  • ADR written if a fork was resolved
  • roadmap ticked and stamped; changelog entry
  • issue closed with a link to the release