pingdotgg / pingdotgg/t3code

[Feature]: Surface Claude Edit/Write before/after text in expanded tool entries

Open
#10,970 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted enhancement via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Summary

Expanded tool entries for Claude Edit/Write calls show file paths but never the changed text — no before/after and no diff. Codex turns already surface unifiedDiff data; the Claude path has no equivalent, so reviewing what an edit actually changed requires leaving T3 or re-reading the file.

Current behavior

  • For Claude edits, the expanded entry carries paths/summaries only. The tool input text (old_string/new_string/content) never reaches the UI in any form.
  • Checked on stable 0.0.40 and on current main: a code search shows no old_string/new_string/unifiedDiff handling in ClaudeAdapter.tsunifiedDiff exists only around the Codex/checkpoint paths, which is a different mechanism (turn-level summaries, not per-edit before/after).

Expected behavior

  • Expanded Edit/Write entries include a bounded verbatim before/after pair (with a truncation flag when the bound is hit), rendered in the existing expandable work-log row — no new UI surface needed.
  • Collapsed rows stay exactly as today.

Repro

  1. In a Claude-backed thread, ask the agent to edit any tracked file.
  2. Expand the Edit/Write work-log entry.
  3. The entry shows paths only; the old/new text is nowhere in the UI although it was present in the tool input.

A per-field bound keeps this consistent with the recent payload-slimming direction. Happy to provide fixtures or help validate a bounded-payload design.

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 in ClaudeAdapter.ts and compare its tool-input handling with the existing Codex unifiedDiff paths. Trace how expanded work-log rows receive their data, then add bounded verbatim before/after text for Claude Edit/Write entries with a truncation flag while keeping collapsed rows unchanged. Validate using a Claude-backed thread that edits a tracked file.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.