Crodox - Slice any task out of your codebase. Merge back clean.

by
Crodox isolates any task with its complete dependency closure into a clean, runnable workbench. When you're done, your changes merge back deterministically. Built for teams that ship parallel work without losing context.

Add a comment

Replies

Best
Hi everyone - Philip here, co-founder of Crodox. A few years ago we kept running into the same problem on large codebases: every meaningful task touches files and dependencies that live far apart, but the tools we use force us to load the whole context anyway. AI assistants help with the typing - they can't tell you which parts of the codebase actually belong to a task. Worktrees and branches isolate files,not behaviour. Visualization tools show the graph, but you can't act in it. So we built Crodox around a single idea: any task should be physically isolatable. Crodox takes one task description and uses a reverse compiler with language-specific templates to compute its complete dependency closure. The result is a workbench: a smaller, runnable slice of your codebase with exactly what the task needs, nothing else. Tests run. The slice compiles. You hand it off to a teammate, to an AI agent, or to yourself on another machine. When the work is done, Crodox merges the changes back into the source, deterministically without the kind of conflicts you get from rebasing twelve weeks of unrelated work. We call this the Async Developer Workflow: Slice -> Hand off -> Merge back. Today's launch is a free beta. TypeScript, JavaScript, Python and Angular are supported first; C# and .NET are on the enterprise roadmap. It runs as a hosted web app - sign in, connect a repo, slice. No installs, no agents, no rebuild of your pipeline. A few honest things up front: • This isn't an AI coding tool. It is the layer underneath them. • This isn't a visualization tool. The slice is executable. • Templates are language-specific because every language hides dependencies differently. We are shipping the ones we use ourselves first. Three questions I would love feedback on: • Where in your current workflow does context loss hurt most? • Which language or framework should we prioritize after these four? • What would make Crodox a 'drop everything and try this' tool for you? Looking forward to the conversations. Philip

Congratulations on your product's launch!!