1jehuang / 1jehuang/jcode

Feature: Agent Decision Timeline & Replay

Open
#525 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

Problem

When agents work autonomously—especially in swarm mode—it can be difficult to understand how a task progressed. While the final result is visible, developers have limited insight into why specific decisions were made, when tasks were delegated, or how the execution plan evolved.

This makes debugging, optimization, and trust in autonomous workflows more challenging.

Proposed Solution

Add an optional Decision Timeline that records key execution events during a session.

Example timeline:

  • Task received
  • Plan generated
  • Worker A spawned
  • Worker B requested file changes
  • Memory retrieved
  • Browser tool invoked
  • Merge completed
  • Final response generated

Each event could optionally expose relevant metadata (tool used, duration, affected files, or spawned agent) and allow replaying the execution flow from the UI.

Alternatives Considered

Existing logs contain useful information but are chronological and low-level. A structured timeline would provide a much clearer overview of the agent's reasoning and coordination without replacing detailed logs.

Additional Context

This would be particularly valuable for long-running sessions, swarm workflows, and self-development mode by making autonomous execution easier to understand, debug, and optimize.

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

No files, tests, or entry points are named. Start by reviewing the existing chronological logs and the session or UI flow, then define the event metadata and replay scope. Done should mean an optional timeline records the listed execution events and exposes a usable replay view.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai-infra-agents, cli, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.