14,859 sessions · 127,605 messages · 17,271 commits
Your Wrapped → Share| Metric | Mac Studio | MacBook |
|---|---|---|
| Sessions | 14,705 | 154 |
| Messages | 125,520 | 2,085 |
| Commits | 16,960 | 311 |
| Bash Commands | 363,032 | 3,988 |
| Read Calls | 147,477 | 1,307 |
| Edit Calls | 122,791 | 1,148 |
| Write Calls | 41,429 | 486 |
| Multi-File Changes | 291 | 21 |
| Lines Added | — | +98,075 |
| Satisfaction | 59% | 91% |
| Multi-Clauding | 8% | 55% |
On the MacBook, 55% of all messages occurred during overlapping sessions. One of the most advanced Claude Code workflows observed — a central command hub coordinating 6-8+ parallel worker sessions, each targeting different codebases simultaneously.
The #1 time sink across both machines. 149 combined wrong-approach events. Claude locks onto wrong root causes — misdiagnosing env vars when it's bundling, targeting wrong config, choosing wrong strategy.
npm 2FA/token policies, X/Twitter API credentials expiring mid-session, git auth failures. 110 environment issues on studio. npm publish saga required 3 iterations across sessions.
One session overwrites another's deployment. Branches confused. Files in wrong repos. CDN caching serves stale content. 55% of laptop messages during overlapping sessions.
Social network for developers. Presence APIs, artifact sharing, MCP server, Vercel deployments. Led to USV $250K commitment.
Autonomous artist infrastructure. npm publishing, SDK updates, registry, documentation, onchain lookups.
Farmer Fred voice AI, Telegram bots, CRM integration, ElevenLabs/Twilio, multi-agent coordination.
Podcast launches, social content, X API integration, email infra, investor decks, QA-verified metrics.
Coordinating 6-8+ parallel Claude Code sessions simultaneously — central command hub generating prompts, triaging bugs, reading Wire status, delivering executive summaries. Most advanced Claude Code workflow observed.
Zero to deployed production systems in single sessions — Supabase, Vercel, npm, Twilio/ElevenLabs, OAuth. 17,271 commits across two machines in ~6 weeks.
Claude as business ops partner — cheat sheets, decks, QA-verified metrics, follow-up templates. Pivoting between shipping code and crafting strategic docs. USV committed $250K.
Comprehensive testing maintained while shipping at high velocity. 312 multi-file changes (291 studio + 21 laptop) spanning 8+ files each.
You are a high-velocity orchestrator who treats Claude Code as your central command hub. Across nearly 15,000 sessions spanning social platforms, investor demos, podcast launches, npm packages, AI agents, and protocol infrastructure, you operate with a distinctive pattern: broad, multi-objective directives (3-5 tasks per session) with the expectation of autonomous execution.
Your interaction style is impatient delegation with course correction. You launch Claude at a problem, monitor, and interrupt aggressively when it drifts. You snap back control when Claude over-plans, re-verifies completed work, or misreads intent. Satisfaction skews 91% positive — you expect messiness and factor it into your pace.
Most striking: meta-coordination across your entire operation. Parallel agent sessions, Claude generating prompts for other Claude sessions, status synced via "the Wire," sessions as handoff points between machines. Building while fundraising. 367K bash commands, 17K commits, 42K file writes in 6 weeks.
Wrong-approach is your #1 combined friction. Before any fix, list 3 root causes ranked by likelihood with falsification criteria.
110 deployment issues on studio + CDN caching and session collisions on laptop. Never fire-and-forget.
19+ sessions spent on status reconstruction. Standardize HANDOFF.md at session end.
Read docs first. Verify timestamp format, message structure, headers. If auth fails 3x, rebuild from scratch.
Check git branch before editing. Confirm repo. Write to AGENTS.md before deploying.
Your 6-8+ parallel session pattern evolves into self-coordinating swarms. Agents claim tasks from shared backlogs, write status, detect deployment collisions. Launch 10 agents Monday morning, review shipped work by lunch.
Agents run tight loops: deploy, e2e test production, diagnose, fix, redeploy — iterating until checks pass. The npm publish saga and artifact 404 debugging would resolve in minutes.
40% of laptop goals were status checks. Auto-updated PROJECT_STATUS.md after every session — what shipped, what's blocked, what's deployed, next priorities.