Base Code - Let your whole team build on your product
by•
Base Code lets teams work directly on existing codebases from the browser. Connect GitHub, describe changes in plain language, preview them live, and send completed work through standard pull requests.
Replies
Base Code brings existing codebases into a shared browser-based workspace, letting more people on a team contribute without changing the existing development workflow.
Key features:
• Connect an existing GitHub repository
• Describe changes in plain language
• Work on isolated branches
• Preview changes live
• Collaborate across branches and sessions
• Submit completed changes through GitHub pull requests
• Keep existing branch protections, checks, and review processes
Who its for: Product, design, marketing, QA, and engineering teams that want to contribute directly to an existing codebase.
Try Base Code
P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends
the part I'd want to see addressed is what "preview changes live" actually catches before the PR goes out. plain-language changes from a non-engineer are great for velocity, but the failure mode isn't a broken build, branch protections and CI will catch that. it's a change that compiles fine and looks right in the preview but is subtly wrong in a way only someone who knows the codebase would notice, a query that's technically correct but N+1, a permission check that's slightly too loose. does the reviewing engineer get a diff summary that flags "this touches auth" or "this touches billing" type changes specifically, or is it the same review surface as any other PR and it's on them to catch it by reading the diff like always?
Cool that Base Code connects an existing GitHub repo and lets teammates describe changes in plain language instead of touching the codebase directly.
curious about the review side. when a PM or designer opens a PR from here, does the PR carry the original plain language request and the back and forth, or just the diff? back in my agency days the code was rarely the problem. it was the engineer getting a change with zero context on what the person actually wanted. if the request travels with the PR i'd try this with my team.