|
|
|
|
|
|
by michaelgdwn
87 days ago
|
|
|
Interesting approach. One thing I've been thinking about with agent review UIs is the state representation problem or how do you diff what the agent "knew" at step N vs step N+1? If you can serialize the agent's cognitive state at each decision point (not just the code output), you can build much richer "why did it do that?" explanations. Do you support rollback — i.e., if a reviewer rejects step 5, can the agent resume from step 4's state without replaying the whole chain? |
|
|