The problem.
AI-assisted development produces more than code. Plans, sessions, outputs, and review decisions need a home where the person directing the work can see what is happening.
The approach.
Melvin Codes connects a browser workspace to real coding CLI sessions. Planning and execution modes keep the next step explicit; project workspaces, session history, and artifacts make the work easier to inspect.
The application, session service, and coding tools have separate responsibilities. That boundary matters: the interface should help someone direct the work without hiding how it runs.
What’s built.
The implemented workspace supports real CLI sessions, planning and execution, session history, and artifact review. This walkthrough describes those capabilities; it does not claim a measured productivity increase.
A documented September 2026 restoration exercise is part of the operational evidence behind the project. Historical checks describe that exercise, not a promise of future recovery performance.
What are you trying to make possible?
Discuss paid project work, request a call, submit a community idea, or get help with a C4 SaaS product.