[windsignaling]

I think "low-level" is relative to what's being discussed. Low-level for LLMs would have to do with how transformer layers are implemented (self-attention layer, layer norms, etc.) whereas low-level for agents would be the graph structure.

Although I personally don't think the graph implementation for agents is necessarily as established or widely standardized, it's helpful to know about why such an implementation was chosen and how it works.

> the inner workings of the processing, probing agents, and getting into the weeds

These feel to me like empty words... "inner workings of the processing"? You can say that about anything.

[godelski]

I'm not quite sure I agree, but I do get your point. Why I don't quite agree is that the agents are communicating and thus the "in the weeds" part is getting into how that communication is being processed. Which is what makes or breaks agents. How they interpret one another and respond. There needs to be some mech interp for me to really think of something as low-level. I'll put emphasis on the in the weeds part. Nuance and details are critical parts to a low-level conversation.

  > You can say that about anything.

That is true. But it is also true that you can approach any topic from low-level or high-level. So I'm not sure I get your point here.

[windsignaling]

What I meant was, the phrase "inner workings of the processing" doesn't really mean anything at all. i.e. it doesn't convey any useful information about what you're trying to say.

> How they interpret one another and respond.

That sounds like it just falls back to "how LLMs work". It's the wrong level of abstraction in this case, because it's one level down from the topic being discussed here.