You don't get trust in agents by asking for it. You get it by making the reasoning visible.
The question that matters after an agent touches your code isn't "did it work?" It's "what did it do, and why?" — and if that answer lives in a log nobody reads, trust stays where it started: at zero.
Trust is built when you can see each decision, the context behind it, and the trail it left — before, during, and after the work.
That's why visibility is the product, not a feature of it. It's what we built Dap's governance layer around.
More here: https://t.co/Z48nIl9ebC
Startup Day at Xplora UCEMA ✅
Ignacio and Alejandro represented @crunchloopio on September 11, talking with founders and builders about what they're working on and where software fits in.
Thanks to the Startup Day team, See you at the next one.
#StartupDay#Argentina
I don’t think most people understand how much compute usage per person is going to increase as we scale agentic workflows.
I started renting a server with 32 vCPUs, 128 GB of RAM, and NVMe storage for a development project, and my parallel workloads are already maxing it out.
Rails World 2026, done.
Two days at the booth, a lot of good conversations about engineers and agents working in one loop, and one tired team.
Thanks, Austin. More on what we learned soon.
https://t.co/80rRJOBj4A
#RailsWorld#Dap#Crunchloop#RailsWorld2026
Day 1 at Rails World, done.
Dap on screen, stickers on the table, and a lot of good conversations about engineers and agents working in one loop.
https://t.co/80rRJOBQU8
#RailsWorld
Something I see constantly: teams "adopt AI", but every engineer ends up running their own flavor of it.
The intent is good. The consequence isn't: DORA's 2025 research names "a clear and communicated AI stance" as one of the few things that reliably amplifies AI's benefits across a team — and their advice is blunt: "Establish and socialize a clear policy on permitted tools and usage to build developer trust."
Standardizing that across engineers is exactly what lets AI's real impact show up at the team level, instead of getting diluted across individual habits.
This is not a nice-to-have for us — it's the differentiator.
The use case: https://t.co/jrEZGtc1tN
#AI #AgentOps
When your platform unlocks unattended agents, your outcomes can no longer be measured in engineering hours. Curious how teams that have stepped into this territory are measuring things — especially the ones not capped by a subscription.
Agent work is about to show up as a real line item and most teams haven't prepared a budget line for it.
The instinct is to compare against a salary. The better comparison is per unit of work: token spend is a cost you can see, predict, and optimize. Teams that treat agent spend as engineering economics, measured and allocated, will make calmer decisions than teams that treat it as a surprise on an invoice.
We've been running this math on our own platform for a while. If agent work is heading for your P&L, the details are worth your attention: https://t.co/RJuSQFxo0d and https://t.co/2eo9NHQIY3
One week until #RailsWorld.
We’ll be in Austin on Sept 23–24 with a live #Dap demo at the Crunchloop booth.
Come talk about what it takes to run #AI in a real software delivery loop.
Not attending? Explore Dap: https://t.co/uhTSlIssfk
#Rails#Crunchloop#SoftwareEngineering
@notkevinzhang We are building an agentic software development platform, dap (https://t.co/EHRmTywT6V).
We have a lot of interesting decision-making opportunities in our harness, code review process and auto-merge jury.
We would love to try it out!
El viernes pasado estuvimos presentes con @crunchloopio en el StartupDay de @xplora_ucema contando lo que venimos haciendo con @hey_im_dap
Muchas de las empresas con las que hablamos están hasta las manos desarrollando cosas y no llegando con las planificaciones que se tienen. La AI nos da el sentimiento de tener superpoderes pero si no usa bien puede generar más quilombos que beneficios.
Si alguno se siente así dejo los MD abiertos para charlar y contarles cómo lo resolvimos con DAP!