We’re a student-run lab at Pomfret School. We build working tools for the people down the hall. Next up: the people down the road.

Rules of the room

  1. (01)The client talks first.
  2. (02)We read the problem back.
  3. (03)No timeline promised on the first call.
  4. (04)We test with our own data.

Merged: 80 pull requests merged

Pull requests merged since April 2026.

24,000+ lines of code
11 public repositories
5 faculty cases
37 student members

Numbers checked Oct 13, 2026

The club’s public GitHub, recorded when it had 50 merged pull requests: a search, then one of them, which adds plain-English comments to the roster-export code.

The AI is in our workshop, not stamped on your tool. We build with AI coding assistants. None of the four tools we’ve built calls an AI model. Want yours with none? Say so.

Leadership

Cayden Auyang ’27

President. Sits in on every discovery call, assigns the cases, reviews the pull requests, runs the demos.

Cayden’s GitHub (opens in a new tab)

Luke Ryan ’27

Vice President. Oversees every case with Cayden, reviews pull requests, and joins client meetings.

Faculty advisor
Josh Lake

Everyone who makes it happen.

37 students, 2 advisors

Built to hand over.

  • Goal
  • Data source
  • Problem
  • Vision
  1. (01)

    Bring us a problem.

    A form or an email is enough.

  2. (02)

    We fill in the Frame.

    A short recorded call, read back to you before we build.

  3. (03)

    A first working version.

    Shown to you before we build more.

  4. (04)

    Demo, feedback, repeat.

    Every change is a branch and a pull request. Nobody pushes straight to main.

  5. (05)

    Hand it over.

    A live link, or a script in your own Google account.

One click on Create Google Doc, and AutoPlanner confirms the Doc is ready with a link to open it. Demo data.
About a dozen students seated around a long dark conference table, turned toward the camera; a wall screen behind them reads “Club Photo”.
The first official club meeting, November 2025.

From one meeting to eleven repositories.

How it started

  1. Nov2025

    First official club meeting.

  2. Dec2025

    Faculty send in cases.

  3. Apr2026

    First commit, GitHub org, first merged pull request.

  4. May2026

    AutoPlanner demo for the CLC.

  5. May2026

    AI Literacy Week, for the whole school.

  6. Sep2026

    Club fair. One repository per project.

  7. Sep2026

    First meeting of the year. New members join the case teams.

  8. Sep2026

    The first two local-organization projects open.

  9. Oct2026

    AutoPlanner delivered to the CLC.

  10. Oct2026

    Music Studio delivered to the Music Department.

  11. Oct2026

    First meeting with the College Counseling Office.

A student speaks from a lectern in the lower left corner. Above, a large screen under the “Hamilton Hub” sign shows two pictures: a rover on the surface of Mars, and a pill capsule with a boxing glove punching a cluster of cells.
Two students on a sofa watch a talk off to the left; one smiles. Behind them, pizza boxes sit by the windows, with trees outside.

Six months after that first meeting, the club ran AI Literacy Week for the whole school.