Dates

Agents in Action takes place in person on October 16, 2026, from 1–10 PM Pacific in Berkeley, CA.

  • Hacking period: 2:30–8:30 PM Pacific

  • Submission deadline: 8:30 PM Pacific

  • Finalists announced: 9:00 PM Pacific

  • Finalist presentations: 9:00–9:30 PM Pacific

  • Awards ceremony: 9:30–10:00 PM Pacific

Projects must be submitted on Devpost before the deadline.

Eligibility

  • Participation is limited to students accepted through the event registration process who attend in person.

  • Registering on Devpost does not constitute acceptance to the event.

  • Participants may compete individually or in teams of up to five.

  • Each participant may belong to only one competing team.

  • Organizers and judges may not compete for prizes.

Project and Submission Requirements

Build a working prototype with Superhuman Go or Grammarly agents as a central part of the experience.

Each project must enter one primary track:

  • Productivity & Replacement

  • Inclusion & Accessibility

  • Wildcard

Competition work must be completed during the hacking period. Existing libraries, frameworks, APIs, templates, and publicly available tools are allowed, but all pre-existing materials must be disclosed. Previously completed projects are not eligible.

AI-assisted development is permitted. Teams remain responsible for their submissions, including accuracy, appropriate permissions, and compliance with applicable tool licenses.

Each team may submit one project. The submission must include:

  • Project name, selected track, and team members

  • A description of the problem, intended users, and solution

  • An explanation of the Superhuman Go or Grammarly agent integration

  • A short video demonstrating the prototype

  • A source code repository accessible to judges, with setup instructions

  • A working demo link, if available

  • Disclosure of tools and pre-existing code or assets used

Do not include credentials, API keys, or private personal information. Teams must have permission to use any code, content, or data included in their projects.

Finalists must be available for a 1–2 minute live pitch and demo.

Prizes

Prizes will be awarded to the top three projects overall.

The top three projects in each track will also receive commemorative awards, for nine track awards total.

Specific prize items and the format of track awards will be announced before hacking begins. Awards are presented per winning team.

A project may receive both an overall prize and a track award.

Judging Criteria and Winner Selection

Eligible projects will be evaluated using five equally weighted criteria:

  • Impact & usefulness: How effectively does the project address a meaningful problem?

  • Agent integration: How central and effective is the use of Superhuman Go or Grammarly agents?

  • Execution: Does the prototype demonstrate its core functionality?

  • Creativity: Does the project offer an original idea or approach?

  • User experience: Is the project clear, usable, and appropriate for its intended users?

Track awards will consider these criteria within the selected track.

Judges will select six overall finalists for live presentations. Final overall rankings will consider both the submitted project and the live demonstration using the same criteria.

Ties will be resolved first by agent integration, then by impact and usefulness, followed by panel deliberation if needed.

Projects that fail to meet eligibility or submission requirements, misrepresent their work, or violate the code of conduct may be disqualified. Judges’ final award decisions are final.

Code of Conduct

All participants, organizers, volunteers, judges, sponsors, and partners must help maintain a respectful and welcoming environment throughout the event and its associated online spaces.

Harassment, discrimination, intimidation, stalking, unwanted sexual attention, inappropriate physical contact, and deliberate disruption are prohibited. This applies regardless of identity, background, disability, religion, or technical experience.

Respect personal boundaries and requests to stop unwanted behavior. Ask before photographing or recording individuals, and respect requests to opt out.

Projects, presentations, and event communications must follow the same standards.

To report a concern, contact Heba Alazzeh or an MTC organizer at check-in, or message Heba directly through the MTC Berkeley Slack. Organizers will respond to reports and may issue warnings, remove individuals from the event, or disqualify teams depending on the circumstances.