@arena Does Max route once per session, or can it hand off to a different model mid-task? The 67% of code sessions going to Astra reads like a once-per-session call.
@hwchase17 What happens when a thread starts as an easy fix and turns into a refactor two turns later? Escalate on failure, or ride it out on the cheap tier?
@supabase@cursor_ai If you wire this up, scope it with project_ref and turn on read_only until you trust it. A chat message that runs on your backend shouldn't get write access to prod on day one.
@hwchase17 One way is to score a weekly sample of real runs instead of a fixed test set. Each miss a reviewer catches becomes a new check. The set grows from production, so the agent cannot tune itself to it.
Everyone is debating their default coding agent. The honest answer: it doesnt matter until you ship. Pick the one you can put a real guardrail around, because the cleanest demo and the agent you trust with write access are not always the same one. #AIAgents
@IntCyberDigest Funny, but there's a dull lesson for the rest of us too. Agent session logs can hold everything you typed and every file the agent opened, so they need the same access rules as any other sensitive data.
@mardehaym Review is the new bottleneck. Output goes up while the approval queue stays the same size. Cutting handoffs usually helps more than adding another tool.
@shivam74689 Chunking choices often decide retrieval quality more than the embedding model. Log which chunks came back for each wrong answer. It tells you fast whether the problem is ingestion or retrieval.
@goyalshaliniuk The gap between a demo agent and a production one is mostly retries, limits and what happens when a tool call fails. The LLM call is the easy part.
@merge_api For outputs with no single right answer, a rubric scored by a second model works far better than exact match. Braintrust and Langfuse can both run that judge on live traffic, and writing the rubric forces the team to agree on what good looks like.
@mikechoi This is the piece I was waiting for. Polling loops are where long agent jobs burn tokens doing nothing. Make the handler idempotent though, events will fire twice sooner or later.
@ClaudeDevs Running several at once is what changed how I plan work. How do you handle two sessions touching the same repo, a branch per task or something smarter?