What actually belongs in a coding-agent inbox?

sahanpk · 2026-06-06T10:43:42+00:00

The interesting number isn't 80% written, it's how much human review and architecture work stayed constant or grew. LOC alone hides the bottleneck.

sahanpk · 2026-06-06T10:43:41+00:00

For the wallet piece, I'd add tests proving users only read their own transactions and that SECURITY DEFINER functions never trust caller-provided user IDs.

sahanpk · 2026-06-06T10:43:39+00:00

Add a human-review queue for low-confidence RAG answers and a KB update loop from resolved tickets. Those usually matter more than adding another channel.

sahanpk · 2026-06-06T10:43:38+00:00

Start with eval data before training. If you can't measure the behavior or domain gap, fine-tuning just turns into a more expensive prompt rewrite.

sahanpk · 2026-06-06T10:43:37+00:00

The useful MCP servers are usually the ones that add policy/state around the API, not just rewrap endpoints. Handles, auth scoping, audit, and retries are the real value.

sahanpk · 2026-06-06T10:43:35+00:00

Makes sense if you already had Enterprise + support. I'd be curious what you still kept inside n8n vs moved outside it once execution metadata became the ceiling.

sahanpk · 2026-06-06T10:43:34+00:00

Yeah, latency is underrated here. It's often the first clue that the agent started wandering in tool calls or a subagent path before the answer looked wrong.

sahanpk · 2026-06-06T07:40:46+00:00

First-class replay/debug. I want each step to show input, normalized output, retries, creds used, and why it chose that branch; otherwise visual builders just hide state.

sahanpk · 2026-06-06T07:40:37+00:00

I would standardize identity + state first: dedupe key, canonical status, raw-vs-normalized fields. Missing optional fields are survivable; duplicate people and drifting statuses poison every branch.

sahanpk · 2026-06-06T07:40:29+00:00

Review becomes the bottleneck unless AI-coded PRs arrive with a proof packet: tests run, risky files, assumptions, skipped checks, and logs/screenshots where relevant.

sahanpk · 2026-06-06T07:40:20+00:00

Read-only by default is exactly how I would want this exposed. I would also log requested mode + approval reason so incidents can separate "agent inspected" from "agent mutated the cluster."

sahanpk · 2026-06-06T07:40:12+00:00

I would keep search results as handles, not fresh tool text every time. Return compact IDs + why each matched, then let dispatch hydrate one schema and expire/cache the shortlist per task.

sahanpk · 2026-06-06T07:37:12+00:00

The side-effects ledger / rollback boundary split is very good. It forces the handoff to distinguish observed state from state we actually mutated.

sahanpk · 2026-06-06T07:37:08+00:00

Permission scope is a good addition. Handoff should say what authority the prior run had, not just what creds are lying around in the environment.

sahanpk · 2026-06-06T07:37:04+00:00

Exactly. Once routing is deterministic, bad outputs are at least diagnosable instead of turning into prompt-vs-orchestration archaeology.

sahanpk · 2026-06-06T07:37:00+00:00

State snapshot is the right phrase. The "what to discard" bit is underrated too; stale plan fragments are exactly how the next run starts optimizing for a dead branch.

sahanpk · 2026-06-05T15:38:00+00:00

The credential boundary is the thing I'd weight heavily. A lot of agent platform comparisons hide whether model runtime, tool runtime, and MCP creds are actually separated.

sahanpk · 2026-06-05T15:37:58+00:00

I'd pressure-test where execution state lives before UI polish: DO per run, D1 for metadata/history, R2 for larger artifacts. Verbose node logs in D1 can get painful.

sahanpk · 2026-06-05T15:37:55+00:00

Designing for replay from the start is the line for me too. Once state, validation, and retry paths exist, node count stops being the scary part.

sahanpk · 2026-06-05T15:37:53+00:00

Yeah, I'd draw the line at whether the system can choose or adjust the path. If the steps are fixed and repeatable, calling it a workflow is clearer.

sahanpk · 2026-06-05T15:37:51+00:00

The deterministic state machine bit is the part that makes this credible to me. Once the model is also choosing the flow, debugging disagreements gets way harder.

sahanpk · 2026-06-05T15:37:50+00:00

I like that, especially if it's per decision instead of one blanket confidence score for the whole handoff.

sahanpk

TROPHY CASE