What is the best workflow for AI agents in monorepos?

S

Suki Tan

Platform engineers

6d

I am trying to get a realistic read on what is the best workflow for AI agents in monorepos.

Discuss package boundaries, build targeting, caching, and ownership rules.

What has actually worked (or failed) for your team? Specific examples, pricing traps, or vendor claims that did not hold up are especially useful.

285views6replies
E

Elio Marchetti

Product manager

5d

Source quality beat model size for us. Clean knowledge + tool scopes fixed more hallucinations than switching models.

S

Sage Whitfield

Product manager

4d

Start with one bounded workflow that has a clear success metric. We tried to automate three use cases at once and none of them got good enough to ship.

R

Rina Deshmukh

Operations lead

3d

The vendor demo is not the product. Ask to see the same workflow run on your data, not their sample data. That is where connector gaps and permission issues show up.

T

Theo Lang

Customer success lead

3d

Measure rework, not just throughput. An agent that resolves 80% of cases but creates 30% more manual cleanup is not saving time.

Y

Yara Mendes

Senior engineer

2d

We learned the hard way that 'human in the loop' is not a checkbox. If the approval UI is buried or slow, reviewers will batch-approve without reading.

C

Cass Ortega

RevOps practitioner

21h

Security questions should be part of the first demo, not a procurement afterthought. Ask about retention, sub processors, prompt-injection testing, and audit logs before you waste time on a trial.