jasendo

4 ms·

1.
by jasendo 5mo ago
Looks great! Haven't found anything that's abstracted this much of the agent building process out before.
2.
by jasendo 7mo ago
This looks awesome! Excited to see what happens
3.
by jasendo 8mo ago
"Each conversation is writing an invisible roadmap you need to materialize". 100%. Most teams treat observability as a checkbox, not a product feedback loop.
4.
by jasendo 8mo ago
This is actually insane. How do agents secure funding, and do sales, and market, and hear customer feedback and actually accomodate for it?
5.
by jasendo 8mo ago
Interesting take on building your own orchestration layer. What's the core advantage you're seeing with Adama over existing frameworks? Curious if you've hit any walls with reliability or if the control trade-off is worth it.
6.
by jasendo 8mo ago
Really like the framing of "Time to Accountability" as the bottleneck. Curious how you think about this for the orchestration layer specifically. A lot of agent frameworks give you observability into the graph. You can see which n
7.
by jasendo 8mo ago
Cost attribution gets even worse when you factor in the bad decisions. Retries, abandoned tool calls, and cascading failures that still hit your bill but never show up in traces.
8.
by jasendo 8mo ago
The 'you can review code you can no longer write' line is so real. That's the gap that sneaks up on you. Easy to miss until you're three layers deep in something you merged last week.
9.
by jasendo 8mo ago
Context compression is necessary but it's treating symptoms, not the disease. The core issue is that most agent architectures bolt long-horizon reasoning onto models that weren't designed for it. Summarization, filesystem offloadi
10.
by jasendo 8mo ago
Nice framework. Makes me wonder if the future is better external memory, or models that just handle context natively without the retrieval layer.
11.
by jasendo 8mo ago
Interesting approach. Curious how you think about the tradeoff between external memory systems vs. models that manage their own context natively. It feels like the industry is split on which layer should own this.
12.
by jasendo 8mo ago
Solid survey. The breakdown of in-context vs post-training reasoning is a helpful lens. Curious to see how the "long-horizon interaction" challenges they flag get addressed in practice.
13.
by jasendo 8mo ago
Interesting approach. Progressive disclosure helps with token limits, but I'm curious how you handle state across multi-step tasks where Layer 2/3 context from an earlier step becomes relevant again later? The "lost in the mi
14.
by jasendo 8mo ago
The sub-agent context isolation tradeoff is real. We've been experimenting with pushing context management into the runtime itself, with the model deciding what to keep, what to prune, what to pull back in, instead of manually feeding
15.
by jasendo 8mo ago
We've been working on a similar problem, but went the route of pushing this into the model and runtime layer instead of the orchestration layer. Less scaffolding, more baked into how the model reasons. Happy to share more if useful