Terms

Terms of use

Last updated

Repo Fleet edits the workflow files in your GitHub repositories and opens pull requests there, through a GitHub App you install. Using it means agreeing to this page. Repo Fleet is early and in testing, and these terms are written to be read in a few minutes: what it does, what stays yours, and what you take on when you let agents work on your code.

What Repo Fleet does

Repo Fleet is the web app at app.repofleet.ai and a GitHub App you install on your account or organization. Once you link an installation, the app does four things:

  • It reads the repositories that installation grants, and the workflow files under .github/workflows in each.
  • It lets you edit those files, checks them for mistakes, and saves your edits as a commit to the branch you were viewing, or as a new branch with a pull request.
  • It offers a starter pipeline to a repository with no workflow yet, and writes it when you confirm.
  • It lists each repository's workflow runs.

Everything it writes goes through the permissions the installation granted: reading metadata and runs, and writing contents, workflows, and pull requests. It touches nothing an installation did not grant.

The workflows it writes are agents, and they run on GitHub Actions in your own account: on your runners, with the model key you put in your repository's secrets, and with the token GitHub gives each run. Nothing runs on our servers on your behalf, and we hold no key of yours.

Your account

You sign up with an email address, which is also your user name, and a password. You confirm the address before you can sign in, and you keep it working, since it is how we reach you.

  • One account per person. Keep your password to yourself, and tell us at once if you think someone else has used it.
  • What is done while signed in as you is yours to answer for.
  • Link only accounts and organizations you may install apps on. GitHub decides who may install; an installation you link is yours alone in Repo Fleet, and nobody else sees it.
  • You must be old enough to hold a GitHub account.

What we store about you, and how to have it deleted, is in the privacy policy.

What stays yours

Your code is yours. So is everything an agent writes into your repository, whether through Repo Fleet or through a workflow it wrote: commits, branches, pull requests, comments, and files. We claim no right in any of it, and it carries whatever licence your repository already carries. The starter workflow and the templates we hand you become part of your repository the moment they land there; change them however you like.

Repo Fleet itself stays ours: the app, this site, the name, and the logo. These terms let you use it. They do not let you copy it or offer it to others as your own.

What you are responsible for

Repo Fleet writes agents. You run them, and what running them costs and produces is yours:

  • The agents you configure. You choose the model, the prompt, the schedule, what an agent watches, and where it may push. An agent does what its workflow says, on every run, until you change or remove it. Read what a template does before you confirm it; the starter pushes straight to main.
  • What they produce. A commit or a pull request an agent made is yours to review before it ships, exactly as if a colleague had written it.
  • The runner minutes. Every run is a GitHub Actions run in your account, and GitHub bills the minutes to you under your plan. A schedule that fires every fifteen minutes wakes close to three thousand times a month, whether or not there is work.
  • The model costs. Each run calls the model with the key in your repository's secrets, and your provider bills you for the tokens. We never see that bill, cannot cap it, and add nothing to it. Set spending limits with GitHub and with your model provider; that is where they work.
  • Their rules. Whatever runs under your key and your token keeps to GitHub's terms and your model provider's.

Repo Fleet itself costs nothing today. If a plan with a price comes, this site says so before anything is billed, and it changes nothing above: runner minutes and model tokens stay between you, GitHub, and your provider.

Acceptable use

Use Repo Fleet on repositories you may change, for work you may do. Do not:

  • Point an agent at a repository, account, or organization you have no right to change.
  • Use it, or an agent it wrote, to break the law, to send spam, to mine or spread malware, or to harass anyone.
  • Probe, overload, or try to break the app, or try to reach another user's account, installations, or data.
  • Copy the app or offer it to others as your own.

If you find a security hole, write to hello@repofleet.ai rather than using it. We acknowledge within a working day and fix as fast as we can.

When we suspend an account

We suspend or close an account when it breaks these terms, when it is used to attack the app or anyone else, when GitHub asks us to because of the installation behind it, or when keeping it open would put other users at risk. We email you when we do, unless doing so would help an attack.

Suspension stops the app for you. It does not touch your repositories, and every workflow already in them keeps running until you change it, because those run on GitHub, not with us.

No warranty on what agents write

Agents are language models. They are useful and they are fallible: what they write can be wrong, slow, insecure, or infringe something, and it can look right while being none of those. Review agent output the way you review any pull request, and run your tests before you merge.

Repo Fleet is provided as it is, while it is in testing. We do not promise that it is free of faults, that it is up at any given moment, or that a workflow it writes or a change an agent makes is correct, safe, or fit for what you need. If it breaks something, we want to hear about it, and we fix what we can. That is the remedy.

Our liability to you for anything to do with Repo Fleet is capped at what you paid us for it in the twelve months before the claim, and today that is nothing. We are not liable for lost data, lost revenue, the cost of a run that went wrong, or any other indirect loss. Consumer law where you live may give you rights these terms cannot take away; nothing here tries to.

Changes to these terms

When these terms change, we change this page and move the date at the top. A change that matters to you, such as a new charge or a new rule, is emailed to the address on your account before it takes effect. Using Repo Fleet after the date means you accept the terms as they then read. If you do not, end the agreement as the next section says.

Ending the agreement

You end it whenever you like. Uninstall Repo Fleet from your GitHub account or organization, and no token we mint can touch your repositories again. Email hello@repofleet.ai to have your account and everything linked to it deleted; the privacy policy says what that removes. What is already in your repositories stays there, and stays yours.

We can end it too, by closing your account, with notice by email unless the account is being used for abuse. Whichever of us ends it, what these terms say about ownership, about your responsibility for what already ran, and about the limits on our liability keeps applying to the time the agreement was in force.

Whose law applies

Repo Fleet is built and run from Ontario, Canada, and these terms are read under the law of Ontario and the law of Canada that applies there. If we ever disagree and email cannot settle it, the courts of Ontario decide.

Getting in touch

A person reads hello@repofleet.ai. Write there about anything on this page, including a question these terms should have answered and did not.