The product
Your AI agent for org-wide code changes
Three things in one product: planning the change, generating code across every targeted repo, and coordinating PRs through to merge. Built for the platform teams that run dozens of org-wide initiatives a year.
What Tidra does, end to end
The Tidra workflow runs in six stages. You stay in control at every step.
1. Define the initiative and draft the plan
Describe what needs to change in your own words. Tidra drafts a structured change plan and a name for the initiative, covering which files to touch, what patterns to match, what edge cases to handle, and what success looks like. You and Tidra iterate on the plan together, adding detail, catching gaps, and refining instructions until it's ready to run.
Initiatives are how Tidra tracks org-wide work as a single coordinated effort, not dozens of disconnected PRs.
2. Target the repos in scope
Filter by tag, language, framework, ownership, or recent activity. Pick a subset to test against, or target all repos in scope. You can add and remove repos throughout the initiative.
3. Generate code that adapts to each repo
Tidra clones each repo and reads its structure before generating changes — not just the file tree, but the package manager, framework patterns, build configs, and coding conventions in adjacent code.
That means a Go service and a Python service in the same initiative get different implementations. A repo that still uses io/ioutil gets the migration; one that already has it doesn't. A repo on CircleCI gets the right CI config, not the GitHub Actions one.
Bulk generation runs in parallel across every repo in scope at once.
4. Review and iterate on the diffs
Every generated change is visible as a diff before any PR is created. Review what was changed, compare across repos, and identify the ones that aren't right. Regenerate specific repos with refined instructions, or update the plan and regenerate everything. Keep iterating until the diffs look right.
5. Open PRs across every repo at once
When you're ready, create pull requests across all targeted repos in one action. PRs include clear descriptions, consistent titles, optional signed commits, and a link back to the initiative for context.
The owning teams see a normal GitHub or GitLab PR in their notifications, with a request for review from their CODEOWNERS group. They review, comment, request changes if needed, and merge using the same workflow they would use for any contribution. No new tools to learn.
6. Manage every PR to merge in one dashboard
The part that used to live in Slack threads, spreadsheets, and standups: tracking CI failures, regenerating from feedback, chasing reviews, knowing exactly what's still open. Tidra makes it the dashboard view.
Security and data handling
- ·SOC 2 Type II certified (latest audit available on request)
- ·No training on customer code. Your data is never used to improve our models.
- ·Code is cloned ephemerally to generate changes, then discarded
Built by OpsLevel
Tidra comes from OpsLevel, the engineering team behind the Internal Developer Platform used at hundreds of mid-market and enterprise engineering organizations. We packaged the Maintenance Agent (the engine behind Tidra) as a standalone product for teams that don't need the full IDP.
If you already use OpsLevel, Maintenance Agent is available as part of the platform. If you don't, Tidra gives you the same agent in a lighter package.
Ready to see it on your stack?
Book a 30-minute demo with one of our engineers. We'll walk through actual PRs against sample repos in the languages and frameworks you use.