PO: @ndoschek
Once a user can launch yoloarena from the Theia SCM Repositories view, the next gap is visibility: which worktrees currently have a live session, and what state are they in? Today that lives outside the IDE. This story is about bringing a read-only picture of running yoloarena sessions into Theia, so the worktrees the developer is already looking at show whether something is running against them.
This is deliberately vague on presentation. How best to surface sessions in Theia still needs discussion (a decoration on the worktree node, a dedicated view, a status item, something else), and the first cut should stay a read-only overview. Full yoloarena management from the IDE (stop, logs, network policy, config) is explicitly out of scope here and can be layered on later if the overview proves useful.
Scenarios
Feature: See running yoloarena sessions from Theia
Scenario: A worktree with a live session is recognizable
Given a repository with worktrees in the Theia SCM Repositories view
And one worktree has a running yoloarena session
Then the IDE indicates that worktree has a live session
And shows a minimal read-only summary (for example its state)
Scenario: No management actions in the first cut
Given a worktree with a running yoloarena session shown in the IDE
Then the overview is read-only
And stop, logs, and configuration are not offered yetOpen questions (need discussion)
- Where does this live in Theia: a decoration/badge on the worktree node, a separate sessions view, a status-bar item, or a mix?
- What is the minimal useful set of fields for a read-only summary (state, tool, started-at)?
- How does the IDE learn about sessions: poll the
yoloarena CLI, read session state on disk, or wait for a daemon if one lands?
- How fresh does the view need to be (on-demand refresh vs. live updates)?
Non-goals
- Any session management from the IDE (stop, restart, logs, network policy, config). Read-only only.
- A polished or final presentation. The first cut is a sketch to validate the idea.
Relates to
PO: @ndoschek
Once a user can launch yoloarena from the Theia SCM Repositories view, the next gap is visibility: which worktrees currently have a live session, and what state are they in? Today that lives outside the IDE. This story is about bringing a read-only picture of running yoloarena sessions into Theia, so the worktrees the developer is already looking at show whether something is running against them.
This is deliberately vague on presentation. How best to surface sessions in Theia still needs discussion (a decoration on the worktree node, a dedicated view, a status item, something else), and the first cut should stay a read-only overview. Full yoloarena management from the IDE (stop, logs, network policy, config) is explicitly out of scope here and can be layered on later if the overview proves useful.
Scenarios
Open questions (need discussion)
yoloarenaCLI, read session state on disk, or wait for a daemon if one lands?Non-goals
Relates to