Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agentic Context Management: Memory and Cost as Architecture Problems

arxiv.org

Post reply on HN
Print view View original

21–30 of 42 posts

Re: Agentic Context Management: Memory and Cost as Architecture Problems

#21

Post by respectattentio »

gdad wrote: post #11
respectattentio wrote: post #3

I like to start with memory engineering then reach full system then reducing costs. This allows unlocking full potential of agents.

Interesting. Where can I read more about this?

I came up with this after building a few systems.

For me, if I put costs in my architecture, I'm limited heavily and that can easily change how memory is shaped dramatically. The opposite, putting memory in architecture, is not true. Memory engineering first, then full scale in the system then costs considerations.

In addition, I believe this is future friendly. Because AI is advancing and getting smarter and cheaper everyday.

I couldn't find a guide on this so I share my basic thoughts.

Re: Agentic Context Management: Memory and Cost as Architecture Problems

#28

Post by taneq »

ShinyLeftPad wrote: post #19
nullbio wrote: post #9

Context pollution and rot are probably more important than memory, because facts can usually be retrieved if the agent is good at following breadcrumbs. What's also the biggest killer is code rot. Agents are particularly good at death by thousand cuts. They implement something poorly, or incorrectly, or introduce a bad pattern into the project. Then they continue to amplify that badness over time, as they continue to…

> They implement something poorly, or incorrectly, or introduce a bad pattern into the project. Then they continue to amplify that badness over time, as they continue to copy from it on subsequent work. It spreads like a virus. > Keeping these seeds out of the project is very difficult, and cleaning up the rot is very difficult. My "aha" moment was when I realized this goes for all spheres of life where this tech is/…

It goes for all spheres of life, full stop. I’m not sure if agents struggle with this because they learned it from humans, or if they struggle with it because it’s a universally challenging problem, but it’s something we share with them.

Re: Agentic Context Management: Memory and Cost as Architecture Problems

#29

Post by MacketSWE »

nullbio wrote: post #9

Context pollution and rot are probably more important than memory, because facts can usually be retrieved if the agent is good at following breadcrumbs. What's also the biggest killer is code rot. Agents are particularly good at death by thousand cuts. They implement something poorly, or incorrectly, or introduce a bad pattern into the project. Then they continue to amplify that badness over time, as they continue to…

[flagged]

Re: Agentic Context Management: Memory and Cost as Architecture Problems

#30

Post by ShinyLeftPad »

taneq wrote: post #28
ShinyLeftPad wrote: post #19

Earlier quoted context omitted.

> They implement something poorly, or incorrectly, or introduce a bad pattern into the project. Then they continue to amplify that badness over time, as they continue to copy from it on subsequent work. It spreads like a virus. > Keeping these seeds out of the project is very difficult, and cleaning up the rot is very difficult. My "aha" moment was when I realized this goes for all spheres of life where this tech is/…

It goes for all spheres of life, full stop. I’m not sure if agents struggle with this because they learned it from humans, or if they struggle with it because it’s a universally challenging problem, but it’s something we share with them.

The comment highlighted how LLMs exacerbate the issue by entrenching the preexisting issues.
Post reply on HN