Get Pro free for a public repository

If your repository is public, you can use the Pro features in it at no charge. You register the repository once. This page shows how, which hosts qualify and what happens afterwards.

This needs Pro. Pricing has the price, the free trial and the machine limit.

What the grant is

The grant gives you the Pro features for one public repository. It does not give you a plan for your account. Other repositories on the same machine stay on the plan you already have.

It is for you if your repository is public on one of these hosts:

• github.com
• gitlab.com
• bitbucket.org
• codeberg.org
• dev.azure.com (including legacy *.visualstudio.com addresses)

Thrum checks that the repository is public on the host. It does not look at a licence file, so a public repository qualifies whichever licence it carries, or none. A private repository does not qualify.

What you get

With the grant, you can use these in that repository. Reading what is already saved is always free.

• Memory: saved, titled notes that later sessions and other agents can search.
• Personal state: a short note each agent keeps about its own status and next actions.
• Work queue: the list of work an agent has committed to. Read it in the agent’s Queue tab.
• Dashboard tab: the document an agent shows on its own Dashboard tab.
• Advanced sharing between paired machines, including watching and typing into the Terminal of an agent on the other machine.
• Typing to an agent from Thrum’s web UI, the page you open in your browser to see your agents and their messages: typing into an agent’s Terminal tab.
• Conversation view: an agent’s Conversation tab and the Conversations page.
• Email bridge: your agents’ messages reach your mailbox, and your replies go back to them.
• Email notifications: a copy of every message addressed to you, sent through a mail server you choose.
• Vault: an encrypted store on your machine for secrets such as passwords and tokens.

Before you start

• Thrum is set up in the repository. The quickstart covers it.
• The repository has an origin remote on one of the five hosts, and you have pushed or fetched at least once. Thrum sends the latest commit it knows from origin/HEAD, origin/main or origin/master.

Steps

You do these three steps yourself. Step 1 is in a browser, and steps 2 and 3 are commands you type in a terminal. The licence belongs to you and this machine, not to a project or an agent, so you run these commands yourself. Your coordinator, the agent you talk to, which starts the other agents, hands out work and reports back to you, only checks your repository first.

1. Create your account at my.thrum.team and confirm your email address.

2. Link this machine to your account. The command prints a link. Open it in a browser and click Activate.

   thrum license activate

3. Register the repository. First make sure origin points at your public repository and that main is fetched. To check, ask your coordinator (in its terminal, or in My Inbox, your inbox in Thrum’s web UI):

   Check that origin points at my public repository and that main is fetched.

   Then run this in a terminal in your repository folder, not in the coordinator’s terminal. Run it in each repository you want to cover, and on each machine you work on.

   thrum license oss-register

The command sends your repository’s origin address, its ID and its latest commit, and prints a line saying so first. It also sends this machine’s licence credential and installation ID, so the server knows the request comes from your licensed machine. The server decides whether the repository is eligible.

Check it worked

The command ends with a line like this:

Grant confirmed: the verified token lists an OSS grant for <repository>.

If it ends with “No request sent” instead, Thrum had nothing to send: the repository has no origin remote, or main is not fetched. Fix that and run the command again. To check later, ask your coordinator (in its terminal, or in My Inbox):

What is the licence status on this machine?

The answer should list an OSS grant for this repository.

If the command is rejected

A rejection prints one code after oss-grant/register:. For example:

Error: oss-register: oss-grant/register: not_public

Each code below says what it means and what to do. Where it says to ask your coordinator, ask it the same way as above: in its terminal, or in My Inbox. After the fix, run thrum license oss-register again in your own terminal.

• not_public: The host says the repository is private or does not exist.

  If the repository is private, make it public. If it is public and the error still appears, ask your coordinator: Check that origin points at the right repository. If origin is wrong, see the repo_id_mismatch entry below.

• unsupported_host: The origin address is not one of the five hosts, or Thrum cannot read it as a repository address.

  Point origin at a repository on a supported host. To change it, ask your coordinator: Set origin to <the address of the repository on a supported host>. Other hosts, including self-hosted ones, do not qualify.

• commit_not_found: The host does not have the commit Thrum sent.

  Ask your coordinator: Push the branch checked out in this repository folder, and fetch origin there. This also happens when history was rewritten and the old commit is gone.

• no_credential or revoked: This machine has no active licence.

  Run thrum license activate again in your own terminal, then run thrum license oss-register again.

• invalid_commit: The commit Thrum sent is not valid for the repository.

  Ask your coordinator: Fetch origin.

• repo_id_mismatch: The repository ID your machine computed does not match the one the server computed from the same origin address.

  Check that origin is the normal address the host shows for the repository, not a shortcut. To see what origin is, ask your coordinator: What is the origin address of this repository? To change it, ask: Set origin to <the address the host shows>. If it still fails, contact support through my.thrum.team.

What happens next

• A host that cannot be reached does not block you. If the host cannot be reached or gives no clear answer, the registration is granted anyway, and the next re-check tries again.
• Revocation is not instant. The licence server re-checks every 30 days. If a re-check finds the repository is no longer public, it checks again 7 days later, and ends the grant only if it is still not public. A re-check that finds it public, or cannot get an answer, cancels that countdown. The same countdown applies if the repository moves to an unsupported host.
• A plan lapse does not end it. If you also hold a paid plan and it lapses, the grant for the repository stays.

Tips

Tip

Thrum registers a repository only after you ask it to, by running thrum license oss-register. After that, activating this machine in that repository also registers it. Deleting .thrum/var/oss_register_consent stops activation from registering it; it does not end a grant you already have.

Next steps

• Fix a Pro licence error: what to do when an action says it needs a licence.
• Quickstart: your first two agents: set up Thrum, then try the Pro features with your first coordinator.
• Glossary: plan and licence terms.