How It Works

The Process

1. You describe the change

Tell Tidra what needs to change in natural language. Be as specific as you can:

Example:

"Update the GitHub Actions workflow to use Node 20 instead of Node 16. Update the node-version field in the setup-node action."

2. You select repositories

Choose which repos should receive this change. You can:

Select repositories manually from your list
Use filters (language, topics, etc.) to automatically include repos

3. Tidra reads your code

For each selected repository, Tidra:

Clones the repo
Reads the relevant files (configs, code, documentation)
Understands the current state and structure

This happens in parallel across all repos.

4. AI generates changes

Using AI, Tidra:

Understands what needs to change based on your description
Reads the relevant files in each repository
Generates appropriate code changes adapted to each repo's structure

Example: If some repos use npm and others use yarn, Tidra generates the appropriate changes for each.

This happens in parallel across all repos.

5. You review changes

Before any PRs are created, you see:

Exactly what will change in each repository
A diff showing before/after
Which repos don't need changes (already up to date)
Complexity estimates (low/medium/high)

6. Iterate if needed

If something isn't quite right, you can:

Refine your description with more details or clarifications
Regenerate the code changes with your updated description
Review the new changes

This iteration loop helps you get the changes right before creating any PRs - just like working with Claude or Cursor for a complex task.

7. Tidra creates pull requests

Once you approve, Tidra:

Creates a branch in each repository
Commits the changes
Opens a pull request
Adds a clear description explaining what changed and why

All PRs are created in parallel.

7. You track progress

Monitor all PRs from one dashboard:

See which are open, merged, or blocked
Track overall progress
Identify repos that need attention

What Tidra Can Change

Tidra works with any text-based files in your repositories:

Configuration files:

CI/CD configs (.github/workflows, .gitlab-ci.yml)
Docker files
Infrastructure as code (Terraform, CloudFormation)
App configs (config.json, .env templates)

Code:

Updating import statements
Replacing deprecated API calls
Adding error handling patterns
Updating function signatures

Documentation:

README files
CONTRIBUTING guides
Security policies
Code comments

Anything text-based - if you can edit it in a text editor, Tidra can change it.

Build command execution: Running npm install, pip install, and other build commands to update lock files automatically

Coming Soon

We're actively working on:

Private dependency support: Accessing private packages and internal registries with proper credentials

CI test integration: Running your test suites as part of the validation process

Under the Hood

Secure: Changes are generated in isolated environments. Your code never leaves Tidra's secure infrastructure.

Parallel processing: Tidra generates changes for multiple repos simultaneously, not sequentially

Git native: Works with standard Git operations (clone, branch, commit, push)

Quality and Accuracy

Tidra gives you full control over the quality of generated code:

✅ Review before creating PRs - See exactly what will change before any PRs are created ✅ Iterate on the plan - Refine your description and regenerate until it's right ✅ Your approval required - PRs are only created when you're ready ✅ Standard review process - All PRs go through your team's normal review workflow

Getting started: We recommend testing with 5-10 repos first to validate quality, then scaling up to larger sets.

Next Steps

Use cases - See common examples
Getting started - Create your first initiative
Best practices - Tips for success