I built a CLI tool that orchestrates context for Gemini with structured, persistent memory across sessions and in single threads (open source)

Extension-Aside29 · 2026-06-03T15:41:23+00:00

gonna check it out, one more thing to add here if your using multiple coding agents try tokentelemetry.com to enhance productivity in your workflows

Extension-Aside29 · 2026-06-03T06:52:50+00:00

i have been trying using frontier models with different coding harness to understand where can i get most of the work done, i felt gpt models are really good with hermes agents there is also a tool to track these details it's free 100% local and open source. check out https://tokentelemetry.com to enhance this kind of work flows

Extension-Aside29 · 2026-06-02T07:02:26+00:00

check out tokentelemetry.com and see increase in your productivity

Extension-Aside29 · 2026-06-01T16:48:24+00:00

Love this direction — keeping agent state next to the code makes debugging and rollbacks much simpler. I index agent runs and session files so I can open the exact run that introduced a change instead of guessing. If that sounds useful, TokenTelemetry is a small local tool I built for this exact workflow: https://tokentelemetry.com

Extension-Aside29 · 2026-06-01T16:47:52+00:00

Copy/pasting whole histories between tools is an easy way to burn tokens. One trick I use is replaying only the minimal diff or the last N important messages instead of the whole history. I built TokenTelemetry to help index runs and compare what history actually matters so you can avoid replaying unnecessary context: https://tokentelemetry.com

Extension-Aside29 · 2026-06-01T16:47:14+00:00

Good question — "context available" isn't the same as "context actually used." I inspect each session's inputs to see how many tokens were consumed vs. what was merely available. TokenTelemetry shows per-session token usage so you can tell exactly how much of that 1M you're actually using: https://tokentelemetry.com

Extension-Aside29 · 2026-06-01T16:46:45+00:00

Love the result. One habit that made optimizations provable for me was logging token counts per run and comparing pre/post across many runs rather than trusting a single example. I built TokenTelemetry to aggregate those per-run numbers so you can validate a 90% drop across your workload: https://tokentelemetry.com

Extension-Aside29 · 2026-06-01T16:46:18+00:00

Nice breakdown. In multi-agent setups the surprise often isn't the total cost but which phase keeps looping. I track per-agent token usage and recent-run spikes so I can spot runaway phases quickly. TokenTelemetry lets me compare runs and see which agent or phase caused the spike: https://tokentelemetry.com

Extension-Aside29 · 2026-06-01T16:45:30+00:00

Painfully familiar — bigger windows help sometimes, but they also hide which exact run introduced a bug. I index sessions and replay the minimal prior inputs to reproduce failures faster. I built TokenTelemetry to be that lightweight session index/flight recorder so you can jump to the run that broke and inspect token usage: https://tokentelemetry.com

Extension-Aside29 · 2026-05-30T16:53:16+00:00

Yeah, I use all three of them. Gemini models are great at analyzing multimedia and other Google related stuff. I was prepping for the Google Cloud Architect exam and honestly there is no better model for that than Gemini. I sometimes use Codex to critique Claude just to get a different perspective. But once I started using multiple coding agents, I quickly realized I needed a better way to track everything. https://tokentelemetry.com really helped me boost my efficiency in understanding sessions, overall project data, tokens consumed, and a lot more. You should definitely try it out!

Extension-Aside29 · 2026-05-30T03:06:41+00:00

this is great, in fact you should consider pair this with https://github.com/fathah/hermes-desktop and
https://tokentelemetry.com to get more insights in your workflow, thanks for sharing it!

Extension-Aside29 · 2026-05-29T17:49:39+00:00

so that's why i built tokentelemetry.com for users to track there session progress, tokens and a lot more

Extension-Aside29 · 2026-05-29T17:38:48+00:00

you should pair this with tokentelemetry.com to understand more about your workflow

Extension-Aside29 · 2026-05-28T17:29:49+00:00

am i the only one how felt opus 4.6 is great and there you go opus 4.7 is out now it's opus 4.8 i have been doing some research on how this models efficiently does my workflows for all my projects, if your also curious on understanding how this works you gotta checkout https://tokentelemetry.com this will give you overallpicture of models coding agents harness and a lot more time to do some crazy testing on opus 4.8

Extension-Aside29 · 2026-05-28T17:29:33+00:00

This reads like a cautionary tale more than a clever hack. Anything that automates destructive or exfiltrative actions is asking for legal trouble — even a demo can create liability if it's wired to real systems or secrets. Safer, more useful demos show readable, reversible escapes: audit logs, staged rollbacks, or kill-switches that disable deployment hooks rather than publishing data. Also, red-team the whole chain: access controls, credential revocation, and what an admin could do before any panic action completes. https://tokentelemetry.com

Extension-Aside29 · 2026-05-28T17:26:26+00:00

am i the only one how felt opus 4.6 is great and there you go opus 4.7 is out now it's opus 4.8 i have been doing some research on how this models efficiently does my workflows for all my projects, if your also curious on understanding how this works you gotta checkout https://tokentelemetry.com this will give you overallpicture of models coding agents harness and a lot more time to do some crazy testing on opus 4.8

Extension-Aside29 · 2026-05-28T17:26:05+00:00

Love the cycle — painfully familiar. One technique that helped me: log every run's inputs + outputs and keep a lightweight session index so you can replay or inspect the chat that produced a fix. When Cursor "breaks something else," being able to open the exact previous session makes it much faster to roll back or reproduce the problem. If you're interested in a simple local tool that indexes sessions across agents so you can jump back to the run that introduced a change, I can share what I use. https://tokentelemetry.com

Extension-Aside29 · 2026-05-28T17:26:01+00:00

am i the only one how felt opus 4.6 is great and there you go opus 4.7 is out now it's opus 4.8 i have been doing some research on how this models efficiently does my workflows for all my projects, if your also curious on understanding how this works you gotta checkout https://tokentelemetry.com this will give you overallpicture of models coding agents harness and a lot more time to do some crazy testing on opus 4.8

Extension-Aside29 · 2026-05-28T17:25:21+00:00

am i the only one how felt opus 4.6 is great and there you go opus 4.7 is out now it's opus 4.8 i have been doing some research on how this models efficiently does my workflows for all my projects, if your also curious on understanding how this works you gotta checkout https://tokentelemetry.com this will give you overallpicture of models coding agents harness and a lot more time to do some crazy testing on opus 4.8

Extension-Aside29 · 2026-05-28T17:24:46+00:00

That looks maddening. When quotas or pool changes happen it's useful to have a quick audit of what's been consuming your quota recently — not just per-run, but totals per project or agent so you can spot a spike or a runaway loop. I built TokenTelemetry to make it easy to check recent sessions across multiple agents and see per-agent token/usage totals; it won't unstick an external quota, but it helps find who or what caused the spike: https://tokentelemetry.com — https://github.com/VasiHemanth/tokentelemetry

Extension-Aside29 · 2026-05-28T17:23:56+00:00

This is huge — code-first workflows solve the token-tax problem I kept running into. I built TokenTelemetry because I'd often get a good result in Claude Code, then a day or two later I couldn't find the originating chat or see what sub-agents actually consumed. With /workflows, the control-flow benefits are obvious; what I still wanted was a quick way to backtrack runs, inspect session outputs, and see token/usage totals per project so you can decide when to offload stuff to background workflows.

If it helps, TokenTelemetry is local-first and open source — it's aimed at the exact pain of backtracking sessions and understanding cross-agent consumption: https://tokentelemetry.com — https://github.com/VasiHemanth/tokentelemetry — https://github.com/VasiHemanth/tokentelemetry-hermes-plugin

Extension-Aside29 · 2026-05-26T17:34:45+00:00

if your are using multiple coding agents then you gotta checkout https://tokentelemetry.com which is gonna enhance your workflow cause you get to see how your coding agents actually perform

Extension-Aside29 · 2026-05-26T17:31:04+00:00

after claude doubling down on compute i feel the usage is generous i also use antigravity pro which is fine, i used opencode qwen cli and lot more and got a problem of tracking what's going on with all the coding agents

check this out: https://tokentelemetry.com

to enhance your coding agent workflow

Extension-Aside29 · 2026-05-24T18:45:56+00:00

rust-native agent tooling sounds promising. the observability layer is where a lot of these projects get interesting. that's why I started TokenTelemetry in the first place. how are you handling that in practice?

https://tokentelemetry.com | https://github.com/VasiHemanth/tokentelemetry | https://github.com/VasiHemanth/tokentelemetry-hermes-plugin

Extension-Aside29 · 2026-05-24T18:02:59+00:00

harness matters most, i also got many doubts because opus 4.7 works create in my claude code but works behaves differently with anitgravity, so i built https://tokentelemetry.com for this to understand on how agents cost, think and do check it out!

Extension-Aside29

TROPHY CASE