Has anyone integrated Trace with their existing codebase search workflow?

Been using Trace to map function references across our codebase and it's been helpful, but I'm curious how others handle the output. Do you export the cross-universe references to docs, or keep them in your IDE? Also wondering if anyone's hit performance issues when tracing large projects with thousands of files. Would love to hear your approach.

0

1 Comment

Naomi Suzuki· Jul 7, 2026
We export our Trace findings to a shared markdown doc in our wiki since the team references it constantly, then sync key architectural insights back to our IDE bookmarks using Action Sync—this keeps everyone aligned without duplicating effort. For large projects, we've found breaking traces into module boundaries helps avoid performance bottlenecks; have you considered running Trace on specific namespaces rather than your full codebase at once?
0