Documentation

Project Management

A project is a connected GitHub repository. Once connected, TARS can clone it, work on a branch, run your tests, and open pull requests on your behalf.

Adding a Project

From your dashboard, click Add Project. You'll be prompted for your GitHub repository URL.

1

Enter the repository URL

Paste the full GitHub URL for the repo you want to connect. Both HTTPS and SSH formats are accepted:

https://github.com/your-org/your-repo
git@github.com:your-org/your-repo.git
2

Provide a GitHub access token

TARS needs a GitHub token to clone your repository and open pull requests. See the GitHub Access section below for how to create one with the right permissions.

3

Save and verify

TARS will attempt a lightweight clone to verify the token and repo URL are correct. Once verified, the project appears in your dashboard and is ready for tasks.

Tip: You can add as many projects as your plan allows. Each project has its own task queue — tasks within a single project run one at a time to prevent merge conflicts.

Supported Languages

TARS uses Claude AI to read and write code, so it can work with any language that Claude understands. The following are well-tested and recommended:

  • Python — Django, Flask, FastAPI, scripts, data pipelines
  • JavaScript / TypeScript — Node.js, React, Next.js, Vue, Express
  • Go — services, CLIs, APIs
  • Ruby — Rails, Sinatra
  • Rust — systems, CLIs, WebAssembly
  • Java / Kotlin — Spring Boot, Android
  • Shell / Bash — automation scripts, DevOps tooling
  • HTML / CSS / SCSS — templates, stylesheets, design systems
  • SQL — schema migrations, queries, stored procedures
Mixed-language repos work fine. Most real-world projects span multiple languages — a Python backend with a TypeScript frontend, for example. TARS analyzes your entire repo before writing any code, so it understands the full context regardless of how many languages are in play.

How TARS Accesses Your Repo

TARS uses a GitHub Personal Access Token (PAT) or a fine-grained token that you provide. The token is stored encrypted and is only used to interact with the specific repository you connect.

Creating a Fine-Grained Token (Recommended)

1

Go to GitHub token settings

Navigate to GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens and click Generate new token.

2

Set repository access

Under Repository access, choose Only select repositories and pick the repo you're connecting. This scopes the token to a single repo.

3

Grant the required permissions

Under Repository permissions, enable:

  • Contents — Read and write (to clone and push branches)
  • Pull requests — Read and write (to open PRs)
  • Workflows — Read and write (if your repo uses GitHub Actions)
4

Copy and save the token

GitHub shows the token once — copy it immediately and paste it into the TARS project form. TARS stores it encrypted; you won't see the plain-text value again.

Keep your token safe. Treat it like a password. If it's ever compromised, revoke it immediately in GitHub's token settings and generate a new one. Update the token in TARS via Project Settings.

Classic Personal Access Tokens

If you prefer a classic PAT, grant the repo scope (full repository access). Classic tokens apply to all repos you have access to, so fine-grained tokens are preferred for security.

Project Settings

After a project is created, you can update its settings from the project detail page on your dashboard.

Default Branch

TARS opens pull requests against your repository's default branch (main or master). If you use a different integration branch (e.g. develop), you can override this in Project Settings.

Test Command

Specify the command TARS should run to verify code after it writes changes. Examples:

pytest
npm test
go test ./...
bundle exec rspec

If no test command is set, TARS will attempt to detect one automatically from common config files (package.json, Makefile, pyproject.toml, etc.).

Updating the GitHub Token

If your token expires or you need to rotate it, open Project Settings → GitHub Token, paste the new token, and save. TARS will use the updated token for all future tasks on that project.

PR Labels and Assignees

You can configure a default label (e.g. tars) and assignee to apply to every pull request TARS opens. This makes it easy to filter TARS-authored PRs in your GitHub repository.

Removing a Project

To disconnect a project, open the project detail page and click Remove Project at the bottom of the settings panel.

Removing a project is permanent. All associated task history is deleted and cannot be recovered. Any pull requests already opened on GitHub remain open — removing the project from TARS does not close them.

Any tasks currently in the queue for that project will be cancelled before the project is removed.

Next Steps

Once your project is connected, you're ready to submit your first task. Head over to the Getting Started guide for a full walkthrough.