Launch offerFirst month free on paid plans

#neatHackAI agent hackathon

Build agents you’d trust to run without you watching.

Join DiscordSubmissions closed
Powered bycfo.aientire.io

Submissions closed

Updates on Discord ↗

Dates
October 10–12, 2026
Format
Online
Prizes
$19,000 including credits

Partners

Get started

  1. Register for neatHack

  2. Join the neatHack Discord

  3. Check in and confirm your team

  4. Submit your project

    October 12, 7:00 PM–October 13, 2026, 7:00 AM IST. Quote-tweet your demo, then complete the form.

    Submissions closed

Prizes & people

$4,000 in cash, plus partner credits and neatlogs Pro.

1st place

$2,000cash

+ $5,000Dodo Payments credits

2nd place

$1,000cash

+ $3,000Dodo Payments credits

3rd place

$500cash

+ $1,000Dodo Payments credits

Each winner gets 3 months of neatlogs Pro (worth $1500).

Community winner

$500cash

A separate award for community impact. You can win this alongside a top-three placement.

Credits to build with

AWS
AWS creditsFirst 350 teams to complete web check-in
Crustdata
5,000 creditsEveryone participating
The only track

Build an agent that works (literally)

Build an AI agent, or a team of agents, that completes a substantial task from start to finish. Give it a goal, tools and an environment; let each result guide its next action. All projects compete for the same prizes.

Focus areas

Planning

Break a goal into actionable steps.

Tool use

Choose tools, supply inputs and handle responses.

State

Retain state across steps, runs and failures.

Context

Bring in relevant information; leave out the rest.

Execution

Keep long tasks running to completion.

Recovery

Handle failures and unexpected results.

Verification

Check that results are correct.

Iteration

Use each result to choose the next step.

See example tasks

These examples show the size of task we have in mind. They aren't separate tracks, and you don't have to build one of them.

  • Fix a GitHub issueAn agent investigates a GitHub issue, writes and tests a fix, and proposes the fix.
  • Answer a research question with sourcesAn agent splits a question into smaller questions and gathers evidence for each one. When sources disagree, the agent works out which source to trust and writes an answer with citations.
  • Watch a running systemAn agent watches a running system for unusual behavior. When the agent finds a problem, it looks for the cause and takes an action to fix it.
  • Several agents working togetherSeveral worker agents each solve part of a task on their own. A coordinator agent then combines their results and settles any disagreements.
  • Work while things changeAn agent works on a long task while the environment it works in keeps changing.

Requirements

Use ,and

Your project must use neatlogs, Entire and cfo.ai. Use neatlogs and Entire to build and improve your agent, and cfo.ai to plan its business.

neatlogsWorks with any agent

Trace every agent run

Find the code behind a failure, then compare runs to verify your fix.

  • Model and tool calls, inputs and responses
  • State changes, retries, failures and agent messages
  • Latency, token usage and cost
neatlogs / tracesExample run
Research agentEvery step, in context.
Success
Span treeDuration
  • agentresearch_agent2.84s
  • llmplan620ms
  • toolsearch_documents480ms
  • llmcompose_answer1.42s
  • toolverify_citations320ms
5 spans1.8k tokens$0.003
EntireFor coding agents

Give your coding agent repository context

Open-source tools for understanding your codebase and the history of AI-made changes.

  • Checkpoints: save the context behind each change
  • entire-graph: map relationships across your repository
agent-workspaceExample PR
Preserve state across retries #42

agent/recovery → main

Conversation 2Files changed 1+3 −1
src/agent/run.ts
− const state = createState();+ const state = checkpoint.restore();+ await agent.run(state);+ checkpoint.save(state);
EntireCheckpoint attachedContext, decisions & changes

Plan the business with cfo.ai

Use cfo.ai to plan your agent’s pricing, costs, revenue and runway. Include the resulting business plan in your submission.

neatHack signup & credits

Sign up at cfo.ai/neathacks ↗

A card is required during signup. Immediately after signing up, cancel your subscription in Settings → Billing. You won’t be billed if you cancel immediately.

The neatHack team will provide your cfo.ai credits directly.

cfo.ai / agent economicsExample model
C6ƒx=(C3-C4)/C3
Illustrative monthly economics for two scenarios
ABC
1Monthly modelBaseGrowth
2Customers100250
3Revenue$2,000$5,000
4Infra + inference$400$850
5Gross profit$1,600$4,150
6Gross margin80%83%
Unit economicsRunwayScenarios

Judging criteria

Judges score each project in five categories. Each category is scored out of 100, and the categories are weighted as shown to give a final score out of 100.

The agent

How well the agent, or the system of agents, handles a substantial task from start to finish.

30%

Use of neatlogs, Entire and cfo.ai

How effectively you used neatlogs, Entire and cfo.ai to build, improve and plan a business around the agent.

25%

Demo video

How clearly the demo video explains the agent and your use of neatlogs, Entire and cfo.ai.

20%

Building in public

How you shared your project with other people while you built it.

15%

Usefulness and originality

Whether the agent solves a problem that people have, in a new way.

10%
Evidence & verification

Back up each claim in your submission with evidence that judges can check.

The agent improved
A run before your change and a run after it, e.g., two neatlogs traces, with the numbers you compared
You used neatlogs
Links to neatlogs traces from your project, or screenshots of them
You used Entire
Checkpoints or entire-graph output from your repository
You used cfo.ai
A business plan covering your agent’s pricing, costs, revenue and runway
The agent recovers from failures
A run where an action failed, showing what the agent did next
You built in public
Links to what you shared during the hackathon, tagged #neatHack
You wrote the code during the hackathon
A public repository with commits dated during the hackathon

Schedule

Build October 10–12, submit October 12. Winners are announced October 16. All times below are in IST.

October 10

Day 1

  1. 9:00 AM IST — Kickoff call

    We’ll kick things off with TheVibeFounder, a surprise workshop (more on this later tonight), and a Q&A before everyone starts building. We’ll also introduce you to the judges and mentors, who’ll share more about the kind of projects they’re looking for during the hackathon.

  2. 12:30 PM IST — Hackathon begins

    We’ll transfer AWS and CrustData credits to you.

  3. Workshops & office hours

    Technical sessions and support from neatlogs and sponsors.

October 11–12

Workshops & submission

  1. Final workshops & office hours

    Sunday, October 11 — The last round of technical support before submissions.

  2. Submit & share on X

    12 October, 7:00 PM–13 October 2026, 7:00 AM IST

    Post your demo video in a public quote-tweet of the official neatlogs launch post with @neatlogs, @EntireHQ and @arithecfo. Then finish the three-step submission form at neatlogs.com/submission with your project, public repo, team and tool details. Both steps are required. neatlogs and cfo.ai will engage with the first 50 quote-tweets. Check Discord for final cutoff updates; the latest deadline posted there is authoritative.

October 16

Results

  1. Winners announced

    We announce the three placed winners and the community winner.

Judges & mentors

Judges

Haimantika Mitra

Haimantika Mitra

Senior developer advocate & forward deployed engineer

Entire
Abhi Singh

Abhi Singh

Solutions engineer · ex-GitHub · ex-BrowserStack

Entire
Ajay Yadav

Ajay Yadav

Founder @neatlogs

Akshay Hangloo

Akshay Hangloo

Head of product engineering @neatlogs

Mentors

Rohan Mukherjee

Rohan Mukherjee

Advancing intelligence

Proximal
@roerohan
Chetan Raj

Chetan Raj

Frontend architect / senior engineering manager

Zinnia
@thecjstream
Ankush Dharkar

Ankush Dharkar

Founder @TrueHuman.id · human trust infrastructure for AI

Rithvik K

Rithvik K

ML engineer · research grantee @Adoption AI · software engineer @Palantir

Building resources

Models, infrastructure and data for your agent.

Nova & Claude models

Access seven models through one OpenAI-compatible API. Team leaders verify their check-in email to get a shared key.

One $20 model budget per checked-in team or solo. Shared across the team; requests stop at the limit.

Compute & infrastructure

EC2, Lambda, IAM roles and load balancers in us-east-1. Bedrock isn’t included; use the separate LiteLLM key for Nova and Claude.

One $25 AWS allowance per team or solo. First 350 teams to complete web check-in.

Company & people data

Give your agent company and people data through Crustdata’s APIs. Useful for research, discovery and enrichment tasks.

5,000 credits for everyone participating

Questions & rules

FAQs01 / 11

When and where is neatHack?

neatHack is a 48-hour online hackathon on October 10–12, 2026, starting Saturday at 12:30 PM IST. The kickoff call is at 9:00 AM IST on October 10. Submissions run from October 12, 2026 at 7:00 PM IST to October 13, 2026 at 7:00 AM IST. Check Discord for final cutoff updates; the latest deadline posted there is authoritative. Winners are announced on October 16.

FAQs

neatHack is a 48-hour online hackathon on October 10–12, 2026, starting Saturday at 12:30 PM IST. The kickoff call is at 9:00 AM IST on October 10. Submissions run from October 12, 2026 at 7:00 PM IST to October 13, 2026 at 7:00 AM IST. Check Discord for final cutoff updates; the latest deadline posted there is authoritative. Winners are announced on October 16.