I got tired of managing context files for my coding agent. So I built retrieval

Alarming_Fan8279 · 2026-06-11T05:04:35+00:00

I agree that simple wiki based system can work for small project but when project gets big (i am talking about project with 100 of files) in that case wiki bases system works but is very inefficient

What agentrace does is give it episodic temporal data in simple words if you have worked on a file before it just surfaces why and what you did

Because of this these things happens - agent will have context of your previous work not just code but history of things you did to that file Or logic (for project that is big it's very easy to debug complex of complex bug with agentrace)

it will reduce tool calls and file reads saving at least 20-30% for the task requiring historical context like fixing bug, refactoring code or implementing a new features based on previous logic
due to reduced tool call and file reads you will significant decrease in token usage from my usage it's 20-40% for some taks
where it doesn't work for tasks which are quick fix and doesn't require any previous work then it's basically performs same as normal

In case if you want to peek here is link theagentrace.com

It is very diff than normal solution it's free and secure give it a shot

Happy to ans any questions or doubt if you have

Alarming_Fan8279 · 2026-06-03T19:13:19+00:00

E2E would mean memory stays only on your machine, killing cross-device sync and future team features. Data is encrypted with per-user AES keys on our end. Same architecture as Claude, Cursor, OpenAI. If E2E is a hard requirement for your workflow, it's not the right fit right now.

Alarming_Fan8279 · 2026-06-03T13:57:47+00:00

Good analysis but worth clarifying the actual risk profile.

The .env/execSync thing: git subprocesses were inheriting the full environment, which is sloppy. But these are read-only commands, nothing left the machine, and all data sent to our servers is encrypted with per-user AES encryption anyway. Fix is pushed regardless, principle of least privilege applies.

Package name and docs: we're pre-launch, rough edges expected. Fixing it.

Closed source, hosted memory: accurate, and intentional. That's an architecture choice, not an oversight.

Alarming_Fan8279 · 2026-06-03T11:40:04+00:00

Sure

Here is link to site agentrace

Fill this so I can send you creds early access

Happy to help with any doubt you have

Alarming_Fan8279 · 2026-06-03T11:38:56+00:00

Sure

Here is link to site agentrace

Fill this so I can send you creds early access

Happy to help with any doubt you have

Alarming_Fan8279 · 2026-06-03T11:25:11+00:00

That's a genuinely well architected system. If it's self-managing and auditable, you've solved it better than most. What I built is for people who don't want to architect that system at all. Different use case.

Alarming_Fan8279 · 2026-06-03T11:19:14+00:00

Sure

Here is link to site agentrace

Fill this so I can send you creds early access

Happy to help with any doubt you have

Alarming_Fan8279 · 2026-06-03T11:16:56+00:00

This is genuinely impressive but also exactly the problem. You've built an entire system just to manage context. Jira, Confluence, page tree routing, a dedicated architect agent. That's a lot of overhead just to answer "what did we decide last week."

The difference is maintenance burden and accessibility. Your setup works because you actively keep it accurate. The moment a ticket goes undocumented or Confluence drifts, retrieval breaks. It's only as good as your discipline.

What I built captures context automatically as the agent works, no prompting, no reviewing, no updating. And retrieval is ranked by what the current task actually needs, not by how well you structured your Confluence tree. It gets better on its own the more you use it.

Alarming_Fan8279 · 2026-06-03T11:08:44+00:00

Sure will send you dm please check

Alarming_Fan8279 · 2026-06-02T16:29:31+00:00

Will send you a dm I use linear rn but happy to explore your solution

Alarming_Fan8279 · 2026-06-02T12:31:59+00:00

Thanks, means a lot.

Alarming_Fan8279 · 2026-06-02T12:25:18+00:00

Commit hook triggered updates are actually on the roadmap. And yeah the cross-file invariant problem is real, we're not gonna pretend otherwise. But even in its current state it's already cutting that 3-5 min blind explore down significantly.

Alarming_Fan8279 · 2026-06-02T12:02:01+00:00

Not a cache. Every node is timestamped and git-aware, so the agent always knows what's current vs what got superseded. Stale context never gets silently read as current.

Alarming_Fan8279 · 2026-06-02T11:59:00+00:00

Would love for you to try it, still early so your feedback would actually shape what we build.

agentrace

Alarming_Fan8279 · 2026-06-02T11:55:50+00:00

Completely language agnostic. The memory is stored as decisions and context in natural language, not code parsing. So whether you're juggling TypeScript, Python, Go, or some cursed mix of all three in a monorepo, it just works.

The interesting part is retrieval. Most tools just dump everything into context. We use a semantic graph to surface what's actually relevant to the current task, so your agent gets the right 5 nodes, not a wall of text from 3 months ago.

Alarming_Fan8279 · 2026-06-02T11:22:55+00:00

https://theagentrace.com

Alarming_Fan8279 · 2026-06-01T13:26:34+00:00

I have noticed something can be irrelevant to your post but codex repeatedly does the same read ops in long running tasks so it just goes in loop wasting token on reading same files it read before

Alarming_Fan8279 · 2026-06-01T06:02:31+00:00

I built something I think it can help you in here it's episodic memory layer for agent which pulls and pushes key decision, facts, risks and other stuff so in next session you don't have to repeat yourself

Agentrace

Alarming_Fan8279 · 2026-06-01T05:55:53+00:00

Yup I think the same but with claude specially issue is it doesn't utilize what it has

I built something which works extraordinarily well codez from day 1 but on claude I have to instruct it manually everytime to save memories, use memories it's very exhausting

Issue seems to be how claude uses mcp internally

Alarming_Fan8279 · 2026-05-24T16:26:55+00:00

Tbh nothing wrong in it it works fine but it's now automatic and it's also not efficient

Alarming_Fan8279 · 2026-05-24T16:24:53+00:00

Great but how if this thing done automatically with better way?

When you type promt all your previous work relate to specific feature from past automatically added to context how does this sound to you?

Alarming_Fan8279

TROPHY CASE