1jehuang / 1jehuang/jcode

Feature: tree-view of the current session traversal (like Pi's tree feature)

Open
#744 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

autonomous: no enhancement priority: medium triage: needs-decision
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

Feature request
Add a tree/exploration view of the current session traversal, similar to the "tree" feature in the Pi coding agent, that lets users see and navigate the branch structure of the current session.

What it should do

  • Render the current session as a tree: the root prompt, branch points, forks, and each parallel/derived thread (e.g. subagents, swarm children, forked panes).
  • Let users traverse the tree to jump to a specific point/thread rather than scrolling a linear transcript.
  • Make visible where the active position is in the tree.

Why it benefits all users

  • Long sessions with forks, subagents, and swarm orchestration quickly become hard to navigate linearly. A tree gives a mental map of how the work is branching and where the current focus is.
  • Encourages a consistent way to inspect and jump across the session graph that today is only partially covered by pane/tab switching and /fork.

Suggested scope
A read-only tree view in the side panel keyed off the existing session/turn graph (forked panes, subagent children, swarm nodes are already tracked), with the ability to select a node and open/jump to that point.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing session/turn graph and the pane/tab, /fork, subagent, and swarm navigation paths. Confirm how a read-only side-panel view can identify the root, forks, child threads, and active position. Done means users can inspect the tree and select a node to jump to its corresponding point or thread.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.