AI coding tools are file-aware. We built Workspai to make them workspace-aware.
We launched Workspai today.
The core problem behind it was simple: backend developers still have to explain their stack, layout, and conventions to AI from scratch in every session.
I had already built RapidKit as the execution layer for backend workspaces. Workspai became the AI layer on top — a VS Code extension that reads the workspace before every AI prompt so the model can work with real project context, not just the current file.
Still early, but this is the clearest version of the product we've had so far.
Would love feedback from anyone building in AI devtools or backend tooling.
Backend developers often waste hours explaining their system architecture to AI models that only understand one file at a time.
The real breakthrough happens when your AI knows your entire stack and conventions before you even type a single line of code.
Do you think making AI workspace-aware will finally stop it from suggesting code that contradicts existing project patterns?
That’s the goal — not to make AI magically perfect, but to remove a big source of contradiction.
If the model knows the workspace structure, installed modules, and team conventions before answering, it’s much less likely to suggest something that fights the existing project patterns.
There’s still a trust layer needed around inspectable actions and human review, but workspace-aware context gets the AI much closer to “useful by default” instead of “generic by default.”
Getting the AI to be "useful by default" by feeding it the entire workspace context is a huge step toward making it feel like an actual teammate rather than just a smart text editor. Eliminating those contradictions in project patterns is exactly what senior developers need to actually trust an AI assistant in a complex backend environment. By the way, I work in PR and media placement for dev tools and AI startups, and this specific angle of "workspace-awareness" is a compelling story for technical publications looking for the next evolution in coding assistants.
Thanks — that’s exactly how I see it too. The real opportunity is not “more AI output,” but AI that understands the actual workspace before it responds. We still need stronger trust, reviewability, and production-safe behavior, but this feels like the right direction for backend teams. And I’d genuinely love your view on which technical publications would best understand that story.
Checking back on this Morteza! I've already shortlisted those backend and DX-focused publications we discussed. Let me know when you're ready to dive into the list—happy to share some insights whenever you have a moment.
Spot on, Morteza! For a deeply technical product like Workspai, outlets that focus on the developer experience (DX) and backend engineering would be the perfect fit.
I’ve actually got a short list of technical publications and journalists who cover this specific 'AI DevTool' niche. Drop me a line at mumerumar5@gmail.com and I’d be happy to share those insights and brainstorm how we can pitch this angle.
Looking forward to it!