Self-Promotion
Show off what you're working on
Start new thread

Claude Code, reimagined as a workspace for business teams

by•
I’m building a new way for working with Claude. At least this is how I prefer to work with Claude and you can try it for yourself as well, it’s free: Why am I doing this when there’s already Claude Cowork? Good question, let me explain: 1. I want to be able to edit the files Claude has generated and want to be able to constantly iterate on the file together with Claude. 2. Instead of seeing a chat interface (which for some reason all companies are leading towards to), I prefer working on my workspace while utilizing AI on the side. 3. I want more clarity and freedom on the markdown files that Claude Code generates. I want to change colors, add notes, highlight certain sections and I want to see all of these in a proper view. Not the weird markdown format. 4. I want to store a version history and the changes on my files so I can know what the AI has changed. Now, Claude Cowork is a great tool but it’s not the workspace I want. It creates the files for me, can read my local folders.. which is all great, but I want to be able to edit or fix the files that Claude has created without changing apps. This is how I work. I don’t just leave my documents to Claude, I fix them right away, which Cowork does not allow. To solve these frictions I later worked with VS Code and opened the terminal on the right. Which was pretty good, but then you get the other pain point; ugly markdown files that you can’t read and understand. That’s when I decided to create Sofos. Why not create a tool that runs Claude Code behind the scenes, while allowing you to edit and fix documents real-time within the same app? And that’s what I did, Sofos is basically: * Turning markdown files to WYSIWYG editor and gives you a proper document view for mds * Running local git for version history * Creating CLAUDE.md, SKILL.md, agents and routines automatically for you and placing them under the correct paths in your directory (folder) * Rendering html files so you can view Claude Code’s output (I use htmls for creating presentations) If you’re someone who has faced similar frictions, try Sofos out and tell me what I can improve. Don’t forget to follow us on producthunt: ...
10 views

Add a comment

Replies

Best

the local-first + plain markdown part makes sense. i checked the team flow too: looks like Sofos uses GitHub underneath for submit/review/publish.

what happens when the reviewer isn't part of that workspace? for example, i send an HTML presentation to a client and they want to change one line. can that note come back against the right file/version and land in Claude, or is external review out of scope for now?

i'm building PreApp for that outside-review handoff. happy to run one non-sensitive Sofos deck through publish -> client-style note -> Claude pull, then send you whatever breaks.

thanks for the feedback 🙏 yes as Sofos runs on local folders, the team flow uses GitHub and is very similar to GitHub desktop. The outside review handoff is what I want to focus on as well, in the later phases. Would love to ideate on that part.

yeah, let's make it concrete. if you have one non-sensitive Sofos HTML deck handy, we can use that exact file. i'll review it like an outside client, leave one line-level note, then we see what comes back into the next Claude run. no need to build a new sample. when you're at your Claude session, i'll send the 3-step setup.