Frame the work once
Every workunit starts with a clear problem and a definition of done. No model has to guess your intent from a chat log.
Keep tasks, decisions, and context across Claude Code, Codex, Cursor, Gemini, and new sessions without re-explaining your product every time.
Workunit keeps tasks, decisions, attempts, and source material where they belong — inside the workunit.
Claude Code
recap again"Paste the repo rules and current decisions first."
Cursor Notes
copied forwardThe same architecture summary keeps getting pasted into every fresh session.
Tasks
out of syncDone in the repo. Todo in the tracker. Unknown in the next AI session.
Slack Handoff
summarize first"Can you explain what changed before I touch billing?" becomes a recurring ritual.
context-handoff.md
manual copyYou're maintaining a ritual, not a system.
Claude Code
"Paste the webhook secret setup and which endpoints are done first."
The session lost track of the Checkout flow, the webhook retry logic, and what's left to test.
decisions.md
- Stripe Checkout over custom form
- subscription status check goes in middleware
- webhook signature verification still failing in staging
Teammate
"Which webhook events are we actually handling? I need to pick up the portal task."
Task State
stalecontext-handoff.md
copy next sessionInclude Stripe test keys, webhook endpoint URL, which events are handled, the pricing page status, and what's blocking the portal task.
repo note
Checkout PR merged but the pricing page branch still has a broken test.
Cursor Scratchpad
paste again"Remind me which Stripe price IDs map to which plans before I touch the gating logic."
test status
Are the webhook test failures real?
model switch
re-explain the billing flow
The app is free-only with no way to collect revenue. Users keep asking for a Pro tier but there is no billing system in place. Integrate Stripe so the product can charge for subscriptions and grow sustainably.
Users can upgrade to Pro via Stripe Checkout, subscriptions renew automatically, and the app correctly gates Pro features based on billing status. Webhooks handle failed payments gracefully.
Decision: use Stripe Checkout instead of custom form
Stripe-hosted checkout handles PCI compliance, 3D Secure, and tax calculation out of the box. Less code to maintain.
Attempt: embedded pricing table broke on mobile
The Stripe embedded pricing table rendered inside an iframe that didn't resize. Switched to a custom pricing page calling the Checkout API directly.
Insight: 73% of Pro interest comes from solo founders
Survey data shows solo founders value unlimited workunits most. The free tier limit should cap workunits, not seats.
Payment Service
System · Handles Stripe API calls and webhook processing
Stripe API Docs
Knowledge · Official integration guide and webhook reference
Claude, GPT, Gemini, Cursor, VS Code, OpenRouter, and the tools around them can all pick up the same workspace memory.
Use any model or coding tool you want. Workunit keeps the brief, task state, decisions, and surrounding context in one place so the next session starts with context instead of catch-up.
Every workunit starts with a clear problem and a definition of done. No model has to guess your intent from a chat log.
Tasks, progress, and blockers live inside the workunit. When a new session starts, the model sees what's finished and what needs attention next.
Context atoms capture decisions, failed attempts, and insights so the next model inherits the why — not just the what.
Assets connect the systems, people, and docs that matter. The workunit gives a model real project context, not just a task list.
The app is free-only with no way to collect revenue. Users keep asking for a Pro tier but there is no billing system in place. Integrate Stripe so the product can charge for subscriptions and grow sustainably.
Users can upgrade to Pro via Stripe Checkout, subscriptions renew automatically, and the app correctly gates Pro features based on billing status. Webhooks handle failed payments gracefully.
Decision: use Stripe Checkout instead of custom form
Stripe-hosted checkout handles PCI compliance, 3D Secure, and tax calculation out of the box. Less code to maintain.
Attempt: embedded pricing table broke on mobile
The Stripe embedded pricing table rendered inside an iframe that didn't resize. Switched to a custom pricing page calling the Checkout API directly.
Insight: 73% of Pro interest comes from solo founders
Survey data shows solo founders value unlimited workunits most. The free tier limit should cap workunits, not seats.
Payment Service
System · Handles Stripe API calls and webhook processing
Stripe API Docs
Knowledge · Official integration guide and webhook reference
Most AI tools only see your current conversation. Workunit lets you describe your entire organization, so AI understands the full context before you even ask.
AI knows who's on your team
Skills, roles, availability
AI knows what you're building
Features, versions, roadmap
AI knows your tech stack
Infrastructure, tools, dependencies
AI knows your standards
Docs, conventions, templates
Stop re-explaining your tech stack, your team structure, or your coding conventions. Document it once, and every AI conversation starts with full context.
No terminal, no git clone, no local environment. Launch an AI agent from the browser — it reads your codebase, proposes tasks, and ships pull requests.
You want to create realistic, actionable tasks for your team — but you shouldn't need to know every corner of the codebase to do it. Run Explore Mode and an AI agent reads your code, understands the problem, and suggests tasks — with file references and effort estimates.
You want a first-pass implementation without leaving your project management tool. Point the agent at a workunit, and it clones the repo, writes the code, runs the tests, and opens a pull request — ready for your review.
Pick a repository, choose an AI model, and hit Start — all the workunit context is already attached. No terminal, no git clone.
A cloud VM spins up, clones your repo, and runs the AI agent. Every step streams back live — you see exactly what the agent is reading, thinking, and doing.
An Explore run reads your codebase and proposes real tasks based on actual files. Accept what makes sense, skip the rest.
An Implement run writes the code, runs the tests, and prepares a PR. You review the diff and merge.
Provision VM
832msUbuntu 22.04 · 4 vCPU · 8GB RAM
Clone Repository
3.2sgithub.com/3615-computer/workunit
Install OpenCode CLI
8.4sv1.2.21 · claude-sonnet-4-6
Explore Codebase
2m 14sRead api/server/services/billing.go
Read web/handlers/checkout.go
Read web/handlers/webhooks.go
Read api/db/schema.sql
Read api/server/services/stripe.go
… 25 more actions
Parse Results
1.1sGenerated 4 tasks from exploration
Analyzed 34 files across 8 packages. Found 3 areas to address for the Stripe integration.
Add idempotency keys to webhook handler
HighCreate subscription status cache to reduce Stripe API calls
NormalAdd integration tests for payment failure scenarios
NormalChanged 8 files
billing/checkout.go | 94 ++++++++ billing/webhooks.go | 67 +++++ billing/portal.go | 43 ++++ middleware/gates.go | 28 ++- 4 files changed, 221 insertions(+), 11 deletions(-)
Passed
Failed
Skipped
Bring your own API keys — no Workunit execution fees. You pay Sprites.dev for the cloud VM and OpenRouter for the AI tokens. We just coordinate.
Whether you're the only one carrying the context or coordinating a small team, Workunit is built for people who already use AI to get real work done.
You're the only one who knows the full context. Workunit makes sure AI knows it too.
Juggle multiple client projects without losing context. Switch projects, AI switches with you.
New team members take weeks to ramp up. With shared context, both people and AI start informed.
Use Claude for code, GPT for writing, Gemini for research. One workspace, every AI tool.
Model Context Protocol (MCP) is the bridge between your AI assistant and Workunit.
# Claude Code
claude mcp add --transport http workunit https://workunit.app/mcp
# OpenCode
opencode mcp add && opencode mcp auth workunit
# OpenAI Codex
codex mcp add workunit --url https://workunit.app/mcp
# Gemini CLI
gemini mcp add --transport http workunit https://workunit.app/mcpAlso works with Cursor, Crush, and any MCP-compatible tool.
# Quick commands
"Create a workunit for the authentication refactor"
"What tasks are blocking the API project?"
"Mark the database migration task as done"
# Or paste any Workunit URL
"Create a workunit for https://workunit.app/projects/371594b8..."
"Let's implement https://workunit.app/.../workunits/aa39c53b..."
"Add a task to https://workunit.app/workunits/f7e2b..."The product should be easy to evaluate on a real project. Free gives you room to test the workflow, Pro keeps growing with you once it becomes part of how you build.
Best for trying Workunit on a real project — no credit card needed.
3 projects
25 workunits per project
2 seats
250 MB file storage
MCP integration and full API access
Per month, once Workunit becomes part of how the team actually operates.
Unlimited projects
Unlimited workunits
Per-seat pricing with seats added as needed
20 GB file storage with add-ons available
Priority support once it's part of the workflow
You don't need a migration project or a full process rewrite. Create one workunit, connect one tool, and see how much easier it is when tasks, decisions, and assets survive the next chat.
Start free. Upgrade once it becomes part of the workflow.