Skip to content

Releases

0.4.0

Choose a tag to compare

@jamescalam jamescalam released this 28 Oct 05:38
d48c1d1

trace 0.4.0: references as {id, name} (node 0.4.0) (#3)

0.3.1

Choose a tag to compare

@jamescalam jamescalam released this 27 Oct 03:59
5896d5f

Trace 0.3.1: hides Linear, Hugging Face, npm, ElevenLabs and Google keys, and opaque keys after a _ (EXT-99) (#2)

0.3.0

Choose a tag to compare

@jamescalam jamescalam released this 25 Oct 05:02
89eda7c

Moves to Pointman's typed extension protocol (#1). Needs a Pointman node 0.2.0 or later.

0.2.1

Choose a tag to compare

@jamescalam jamescalam released this 23 Oct 05:16

Asking for older traces with a time older than any of this machine's now also brings every trace between the first page and that time. When several machines' lists are merged, the time sent is the oldest across all of them, and before this fix a machine with fewer traces answered with none.

0.2.0

Choose a tag to compare

@jamescalam jamescalam released this 23 Oct 02:55

The Live pane lists the last 7 days of traces: a row for each thread agents worked in, with its title, agents, when it ran, and its duration, cost, tokens, calls and errors. Running ones come first. It sends the newest 200, and 200 more each time it's asked. The rows are for a trace navigator to search and filter.

  • Each finished run is summed up once and kept in Trace's state folder. A week of logs on a busy machine (about 2,000 runs, 1.3 GB) reads in a few seconds the first time. After that, only new runs are read.
  • Trace notes the thread that woke each run while the run is going, so a run that never posted still shows under its thread after it ends.
  • Logs are read 4 MB at a time, which keeps memory down on long runs.

0.1.5

Choose a tag to compare

@jamescalam jamescalam released this 23 Oct 00:16

/trace live and /trace thread say they open on every machine running Trace, as the pane does.

0.1.4

Choose a tag to compare

@jamescalam jamescalam released this 22 Oct 22:22

The live and trace panes open on every machine that runs Trace, drawn as one view, and /trace live and /trace thread need no machine named.

Trace 0.1.3

Choose a tag to compare

@jamescalam jamescalam released this 22 Oct 21:17

Each trace, and its agents and runs, say which machine they ran on (machine), so the apps can merge every machine's traces into one view.

Trace 0.1.2

Choose a tag to compare

@jamescalam jamescalam released this 22 Oct 06:07

Keeps each update within the node's limits: a patch of more than 900 operations goes as a whole set, and spans' input and output stop being added once a trace is near a pane's 1 MiB.

Trace 0.1.1

Choose a tag to compare

@jamescalam jamescalam released this 22 Oct 05:04

Hides more credential shapes in span inputs and outputs: AWS access keys, private keys, passwords in URLs, JWTs, Stripe keys, fine-grained GitHub tokens, and any value whose name contains KEY, TOKEN, SECRET or PASS.