1Password increases developer productivity across a distributed codebase with Sourcegraph Code Search and Cody
As 1Password's codebase expanded from two monorepos to more than 200 repositories across multiple GitHub and GitLab instances, developers struggled to find code they hadn't personally worked on and often had to ask colleagues via Slack.
The native code search tools built into GitHub and GitLab were limited to searching within each individual code host, making cross-host code discovery ineffective.
Developers became self-sufficient in finding code across all repositories, while Cody reduced the toil of writing unit tests and making programmatic edits, collectively advancing 1Password's innersourcing initiative.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Developers became self-sufficient in finding code across all repositories, while Cody reduced the toil of writing unit tests and making programmatic edits, collectively advancing 1Password's innersourcing initiative.
What tools did this team use?
Code Search, Cody, Sourcegraph, GitHub, GitLab.
What results were reported?
Repositories in codebase: more than 200 repositories; Developer toil reduction: significantly reduce toil; Time saved on programmatic edits: saved me a ton of time; Unit test cases generated per function: 5 to 10 test cases (source-reported, not independently verified).
What failed first in this deployment?
The native code search tools built into GitHub and GitLab were limited to searching within each individual code host, making cross-host code discovery ineffective.
How is this back office ops AI workflow structured?
Developer searches entire codebase → Code Search returns results → Cody generates unit tests → Cody makes programmatic edits → Cody explains unfamiliar code.