Urgent.News

What's breaking now, across thousands of outlets.

Tech

A local receipt for session evidence and the current Git diff

I built agent-change-receipt for reviewing a coding session after the work is done. It reads one native JSONL session and captures the current Git worktree as a separate source of evidence. The result is a local HTML and Markdown report. The main design choice is to keep the session and worktree evidence distinct. Calls and results are correlated by session ID and call ID. A result counts only…

The article discusses a tool called agent-change-receipt, which is designed to review a coding session after the work is completed. The tool captures the current Git worktree as a separate source of evidence, resulting in a local HTML and Markdown report. The session and worktree evidence are kept distinct, with calls and results correlated by session ID and call ID.

The report focuses on one receipt rather than a live dashboard or a full session history browser. The project is focused on providing a local HTML and Markdown report, with the Git section describing the worktree at report time. The tool is written in Node 20 or newer without runtime dependencies and handles secret masking to best effort.

The project is open for feedback on the report format, the separation between evidence sources, and the native session fields worth supporting.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why a ready-made ID photo failed our browser framing check

Treat head centring as a preference: clamp the crop to valid bounds, then test against the rotated image. That fixed our framing bug.

  • Browser's photo framing check had bug causing ready-made ID photos to fail.
  • Code modified to clamp crop to valid bounds and test rotated image.
  • Issue resolved by considering image content, not just position within canvas.

Fix: 'Address Already in Use' (Kill Stuck Process on Any Port)

The Error You start your local server (Node, Python, Go, Docker) and get stopped in your tracks: Error: listen EADDRINUSE: address already in use :::3000 (or bind: address already in use :8080 ) Why…

  • "Address already in use" error occurs when a port is occupied by another process.
  • Linux/macOS users can use "npx kill-port" to terminate the stuck process.
  • Windows users can use PowerShell's "Stop-Process" command to fix the issue.

More from Sunday 4 October →