We noticed that something strange is happening. We're all writing software with AI, but we are mostly doing it alone, with no real sense of how anyone else does it.
So we made a tool to help you understand how you build with AI.
It reads your Claude, Codex, and Cursor sessions, so you can discover things about how you build.
With time, as more people upload theirs, we'll be able to show you how you compare to other builders.
So far, 233,881 sessions have been uploaded and analyzed.
Here are examples of what people have learned about their coding habits...
This is an experiment from YC. Nobody really knows yet what it means to build well with coding agents, and we are trying to find out.
It looks at the AI session transcripts on your computer. Where you run the command tells it whether to analyze every project at once or just one.
Best for a broader picture across projects. Change into the parent folder that holds your repos, then run.
Best for focusing on a single project. Change into that project's folder (replace ~/path/to/your-project with the real path) and run.
You can use this prompt in Claude, Codex, or Cursor to find all your repos on your machine with AI transcripts, show you the list, and hand back ready-to-run commands for the ones you pick.
You get a builder profile, a snapshot of how you work with AI across five dimensions of steering, execution, engineering, product instinct, and planning.
We name the archetypes we see in your sessions, whether you build like an Architect, a Quality Guardian, a Velocity Machine, or a Night Owl. We also pull out your decision patterns, the signature moves you make when directing the AI, drawn from real exchanges in your transcripts.
Then we point at your growth edge, a few specific things to try next, grounded in your actual sessions rather than generic advice.
Sign in with your email, then run the command in your terminal from the repo you want analyzed. The analysis runs in Docker on your own machine, so you'll need Docker installed and running first. In about 15 to 30 minutes you get your profile back with scores, archetypes, decision patterns, and a growth edge.
Your working tree, your .env files, and your raw transcripts stay on your machine. Only short transcript excerpts go to Claude or GPT so we can summarize and score, and what reaches YC is a small payload of scores, narratives, and redacted decisions. You can read the full breakdown.
Your working tree and .env files are not uploaded to YC. During analysis, transcript excerpts (prompts, agent responses, and snippets of tool calls) are sent to Claude or GPT via our proxy so we can summarize what happened. At the end of the run, a JSON payload of scores, narratives, redacted decisions, and session metadata is uploaded to YC. Full breakdown.
Claude Code, Codex CLI, and Cursor. We read the transcripts each tool stores locally.
Yes. The analysis runs locally in a Docker container on your own machine. Install Docker Desktop (or any Docker runtime like colima or OrbStack) and make sure it's running before you run the command. If the engine isn't up, the script prints exactly how to start it.
15-30 minutes depending on how many sessions you have. You get an email when it's ready.
Yes. Run from a parent directory and pick which repos to include, or pass --project NAME.
Whenever you want an updated profile. Each upload produces a new report; your profile aggregates across all of them.
What's the difference between a report and a profile?
A report is a snapshot of one upload. Your profile synthesizes patterns across all your reports: how you've evolved, what's consistent, where you're growing.
I code on multiple machines. Can I get credit for both?
Yes. Just run the same curl command on each machine. Log in with the same email and your builder profile will automatically aggregate sessions across all of them.
How do I attach my Paxel token to my Startup School application?
Linking your Paxel token boosts your chances of getting into Startup School 2026. Open your reports page and find your token. If you haven't applied yet or you're still on the waitlist, click the attach link to send your token straight to your application, or copy the token and paste it in yourself.
I found a bug or have a feature request. Where do I send it?
Use this form to report a bug or request a feature. For feature requests we like, we'll run your prompt with a coding agent and merge the result.
Report a bug or submit a feature request
Tell us below if you found something broken or want this tool to do something it can't yet. For feature requests we like, we'll run your prompt with a coding agent and merge the result.
Try it on one of your repos and you'll have results in about 20 minutes, with YC covering the cost and your code never leaving your machine. Upload
Link preview
Understand how you build with AI.
We noticed that something strange is happening. We're all writing software with AI, but we are mostly doing it alone, with no real sense of how anyone else does it. So we made a tool to help you understand how you build with AI. It reads your Claude, Codex, and Cursor sessions, so you can discover things about how you build. With time, as more people upload theirs, we'll be able to show you how you compare to other builders. So far, 233,881 sessions have been uploaded and analyzed. Here are examples of what people have learned about their coding habits... This is an experiment from YC. Nobody really knows yet what it means to build well with coding agents, and we are trying to find out. It looks at the AI session transcripts on your computer. Where you run the command tells it whether to analyze every project at once or just one. Best for a broader picture across projects. Change into the parent folder that holds your repos, then run. Best for focusing on a single project. Change into that project's folder (replace ~/path/to/your-project with the real path) and run. You can use this prompt in Claude, Codex, or Cursor to find all your repos on your machine with AI transcripts, show you the list, and hand back ready-to-run commands for the ones you pick. You get a builder profile, a snapshot of how you work with AI across five dimensions of steering, execution, engineering, product instinct, and planning. We name the archetypes we see in your sessions, whether you build like an Architect, a Quality Guardian, a Velocity Machine, or a Night Owl. We also pull out your decision patterns, the signature moves you make when directing the AI, drawn from real exchanges in your transcripts. Then we point at your growth edge, a few specific things to try next, grounded in your actual sessions rather than generic advice. Sign in with your email, then run the command in your terminal from the repo you want analyzed. The analysis runs in Docker on your own machine, so you'll need Docker installed and running first. In about 15 to 30 minutes you get your profile back with scores, archetypes, decision patterns, and a growth edge. Your working tree, your .env files, and your raw transcripts stay on your machine. Only short transcript excerpts go to Claude or GPT so we can summarize and score, and what reaches YC is a small payload of scores, narratives, and redacted decisions. You can read the full breakdown. Your working tree and .env files are not uploaded to YC. During analysis, transcript excerpts (prompts, agent responses, and snippets of tool calls) are sent to Claude or GPT via our proxy so we can summarize what happened. At the end of the run, a JSON payload of scores, narratives, redacted decisions, and session metadata is uploaded to YC. Full breakdown. Claude Code, Codex CLI, and Cursor. We read the transcripts each tool stores locally. Yes. The analysis runs locally in a Docker container on your own machine. Install Docker Desktop (or any Docker runtime like colima or OrbStack) and make sure it's running before you run the command. If the engine isn't up, the script prints exactly how to start it. 15-30 minutes depending on how many sessions you have. You get an email when it's ready. Yes. Run from a parent directory and pick which repos to include, or pass --project NAME. Whenever you want an updated profile. Each upload produces a new report; your profile aggregates across all of them. What's the difference between a report and a profile? A report is a snapshot of one upload. Your profile synthesizes patterns across all your reports: how you've evolved, what's consistent, where you're growing. I code on multiple machines. Can I get credit for both? Yes. Just run the same curl command on each machine. Log in with the same email and your builder profile will automatically aggregate sessions across all of them. How do I attach my Paxel token to my Startup School application? Linking your Paxel token boosts your chances of getting into Startup School 2026. Open your reports page and find your token. If you haven't applied yet or you're still on the waitlist, click the attach link to send your token straight to your application, or copy the token and paste it in yourself. I found a bug or have a feature request. Where do I send it? Use this form to report a bug or request a feature. For feature requests we like, we'll run your prompt with a coding agent and merge the result. Report a bug or submit a feature request Tell us below if you found something broken or want this tool to do something it can't yet. For feature requests we like, we'll run your prompt with a coding agent and merge the result. Try it on one of your repos and you'll have results in about 20 minutes, with YC covering the cost and your code never leaving your machine. Upload Source: https://paxel.ycombinator.com/ Paxel · paxel.ycombinator.com
Comments