Control Challenge 2026Live now, closes 30 Dec

Build a complete AI solution with your team.

Everyone wins.

A six-week contest for gitroots Builder and Scale members. Ship it in a repository governed by gitroots, share the story on LinkedIn, and climb the leaderboard.

Open to Builder and Scale members. Teams of up to 6, or solo.

Prize pool

$5,000

In cash, Claude API credits and gitroots Scale credit.

  1. 1st place$2,450
  2. 2nd place$1,650
  3. 3rd place$900
Every other complete teamA certificate for each member and up to 6 months of Builder free.

Ends in

15 Nov to 30 Dec 2026

39days 23hours 40minutes 20seconds

The brief

With your team, build a complete AI solution: an idea, a working product and the code behind it, developed in a repository protected by gitroots. Then tell the world how you built it.

Who can enter

gitroots members on the Builder or Scale plan. Your team works inside your gitroots workspace, so every teammate needs to be a member of it. Starter workspaces can upgrade to take part.

A complete AI solution

A working product that solves a real problem with AI, not a slide or a prompt. Any stack, any model, any AI coding agent.

Built with gitroots

Develop in a repository connected to your gitroots workspace: protected branches, scoped access for each teammate and agent, and reviewed merges.

Shared on LinkedIn

Publish a post that explains the idea and how your team used gitroots to build it. Use #gitrootsChallenge and tag gitroots so we can find it.

How the competition works

  1. 01

    Form your team

    Registration is open now and building starts 15 November. The captain registers the team from a Builder or Scale workspace and invites up to 5 teammates.

  2. 02

    Build in gitroots

    Connect your challenge repository, set access for each teammate and agent, and ship through reviewed pull requests.

  3. 03

    Share your story

    Post on LinkedIn: your idea, what you built, and how gitroots kept the work under control. Submit the link in your dashboard.

  4. 04

    Final leaderboard

    The contest closes on 30 December. Scores are checked, the final leaderboard is published and every complete team is rewarded.

Three things decide the ranking

One published formula, the same for every team. Scores are checked by the competition team when the period closes.

1 pt

Contributions

For every pull request merged into your challenge repository through gitroots. Trivial or automated changes are excluded on review.

5 pts

Team members

For each active teammate, up to 6. A teammate is active once they have at least 3 merged pull requests.

1 pt

Engagement

For every 10 reactions, comments and reposts on your team's #gitrootsChallenge posts on LinkedIn, counted at close.

score = merged PRs + 5 × active members + engagement ÷ 10

Ties: more merged pull requests first, then the earlier project submission.

Register your team

Open to gitroots Builder and Scale members. Your team is tied to your workspace, so teammates join with the access you already manage there.

Team captain

Registers the team, connects the challenge repository, invites teammates and submits the project and LinkedIn post.

Teammates

Members of the same workspace. They build, review and merge, and can share their own posts about the project.

Solo builders

Welcome too. A solo entry is a one-member team and is scored the same way.

Register with your gitroots account

Team registration happens inside gitroots, where your workspace and repositories live.

  • A workspace on the Builder or Scale plan
  • Your GitHub organization connected to that workspace
  • Teammates who are members of the workspace, up to 6 in total
Sign in to register your team

After signing in you pick your workspace, name your team, choose or create the challenge repository and invite teammates.

New to gitroots?
Start on the Builder plan$19 a month. Starter workspaces can upgrade any time.
Start on Builder

Your LinkedIn post

Tell the story in your own words. A complete post covers four things.

  • Your project idea and the problem it solves
  • What your team built and how it works
  • How you used gitroots to build it: branch rules, scoped access for teammates and agents, reviews
  • The #gitrootsChallenge hashtag and a tag for gitroots

Paid promotion, engagement groups and bought or automated reactions are not allowed and disqualify the team.

LH
Lina HaddadEngineering lead · Root Access
Example post

We just shipped PR Explainer, an AI reviewer that explains risky pull requests in plain language before anyone merges.

Four of us built it in a repository governed by gitroots. Our AI agent worked on its own branch with scoped access, main stayed protected, and every change came back to us for review.

Biggest lesson: give agents narrow access and they become far easier to trust. Try it at pr-explainer.rootaccess.dev

#gitrootsChallenge @gitroots

Leaderboard

Live from 15 November, final after the 30 December close once scores are checked.

No teams on the board yet

Scores appear as soon as the first reviewed pull requests merge.

No losers. Every complete team is rewarded.

A complete team has a working AI solution in its challenge repository and a published LinkedIn post.

  1. 2nd place

    $1,650total value

    Cash
    $150
    Claude API credits
    $100
    gitroots Scale credit
    $1,400
  2. Top prize

    1st place

    $2,450total value

    Cash
    $250
    Claude API credits
    $200
    gitroots Scale credit
    $2,000
  3. 3rd place

    $900total value

    gitroots Scale credit
    $900

Every other complete team wins too.

Each member gets a digital participation certificate, and the team earns free months of the Builder plan by final placing.

Certificate

Every member of a complete team

6 mo

Builder plan free

Places 4 to 10

3 mo

Builder plan free

Places 11 to 25

1 mo

Builder plan free

Every other complete team

Free months are applied as credit to the team's gitroots workspace, are non-transferable and have no cash value. They're in addition to the $5,000 prize pool.

A certificate for every builder

Each one has its own verification link at gitroots.com/challenge/verify and lists the exact prize or reward earned. Pick one to look closer. The names below are examples.

gitroots
GR-CC26-0001
gitroots.com/challenge/verify/GR-CC26-0001

gitroots Control Challenge 2026

Certificate of Achievement

1st place

Presented to

Lina Haddad

Captain of Root Access, for building PR Explainer, an AI reviewer that explains risky pull requests, with a team of four in a repository governed by gitroots.

Prize package

Cash$250
Claude API credits$200
gitroots Scale credit$2,000
Total value$2,450

Competition period

15 November to 30 December 2026

Shawki Aladdin

For gitroots

Every certificate carries its own verification link and QR code, so anyone can check it is real.

Open 1st place full size

What's in the pool

$400 in cash, $300 in Claude API credits and $4,300 in gitroots Scale subscription credit, for a combined advertised value of $5,000. Scale credit is valued at $300 per year.

Prize conditions

Prizes are non-transferable, can't be resold and can't be exchanged for cash. Credit applies only to the winning team's gitroots workspace.

Redemption

How long credit lasts, how it's redeemed and its limits are in the official terms. The competition is organized by gitroots and is not sponsored or endorsed by Anthropic.

Fair play

What we expect

  • Original work built during the competition period
  • Code developed and merged through your gitroots-connected repository
  • Honest posts written by your team
  • Teammates who are real members of your workspace
  • Respect for other teams, reviewers and the community

What disqualifies a team

  • Bought, automated or engagement-group reactions
  • Padding the score with trivial or automated pull requests
  • Fake or duplicate member accounts
  • Projects copied from someone else
  • Harmful, deceptive or unlawful AI use

Questions, answered carefully.

Runs 15 November to 30 December 2026. Team rules, scoring checks and prize redemption are set out in the official terms.

Who can enter?

gitroots members whose workspace is on the Builder or Scale plan. Every teammate must be a member of that workspace. There's no separate entry fee.

What counts as a complete AI solution?

A working product that uses AI to solve a real problem, with its code in your challenge repository and a way for others to see it working, such as a demo link or video.

Can we use AI coding agents?

Yes. Agents are welcome, as long as they work through gitroots with their own scoped access. Merged pull requests count the same whoever wrote the code, but trivial or automated changes are excluded on review.

Does the repository have to be public?

No. It must be connected to your gitroots workspace so contributions can be counted. You decide what to show publicly.

How is engagement counted?

Reactions, comments and reposts on your team's LinkedIn posts that use #gitrootsChallenge, checked by the competition team at close. Bought, automated or engagement-group activity disqualifies the team.

What if my team doesn't place?

Every complete team wins something: certificates for every member and free months of the Builder plan by final placing.

When does it start and end?

It opens on 15 November 2026 and closes at the end of 30 December 2026. Work merged and posts published after the close don't count. The final leaderboard is published once scores are checked.

How will winners receive their prizes?

After the close, the competition team checks the final scores and contacts each team's captain. Delivery follows the official terms.

Published before 15 November

Official competition terms

Published here before the competition opens on 15 November 2026. They cover eligibility, the competition period, the scoring formula, how engagement is checked, tie-breaking, prize redemption and how winners are verified.

Join the Challenge View Leaderboard