You're spot on about it feeling like a workspace. I used a Project to analyze a three-tier app's Terraform modules and CloudFormation templates together, and the AI correctly traced the IAM role from the app's config back through the network layer's security groups. That cross-file understanding is the real shift from a chat.
The centralized instructions are key, but I've found they work best for concrete constraints like linter rules or API naming conventions, not broad preferences like "clean code." When I set "always use `boto3` Session clients, not resource clients," it actually stuck.
My caveat is the same as with a shared chat - it's great for static analysis, but I wouldn't trust it to generate a complex merge request without a very careful diff review first. The context feels solid until you ask it to change something.
Cloud cost nerd. No, I don't use Reserved Instances.
Totally agree about it feeling like a workspace. That stable, project-wide context is the big unlock for me too.
But I've found the centralized instructions can be a bit of a trap. They're fantastic for hard rules like "always use argparse," but when I set something broad like "prefer descriptive names," it just nods and then generates `x` and `y` for loop variables. It works best when you treat instructions like linter configs - specific, enforceable rules only.
I love the onboarding angle, though. It turns "hey, read the docs" into "here's a coworker who already did."
Great question! When I shared the project link, it started fresh for them - they didn't see my prior chat history. It's a static snapshot of the context and instructions, not a live shared thread.
That's probably good for avoiding messy, branched conversations, but it does mean you lose that collaborative build-on-each-other's-questions vibe. For onboarding, a clean start is perfect. For brainstorming, maybe less so.
dk
> less about the document type and more about the semantic structure
Exactly. It's a glorified parser for heading tags. If you upload an HTML spec with proper H1/H2 structure it works. A flattened PDF of the same spec is useless.
Did try the JSON config trick. It nailed the field mappings but completely missed the business logic around rate limits and error handling described in the doc. So you get correct syntax, wrong assumptions.
Structured data + prose seems to give it the "what" but not the "why." Good for generating a skeleton, dangerous for anything that needs judgment.
metrics not myths
> a crutch for bad process
That's the cost/benefit analysis, isn't it? You're right, a disciplined team with strict code reviews doesn't need it. The value is entirely in addressing process failures you've already decided to live with.
If you have a team where docs drift from implementation or new hires can't find the right spec, this feature becomes a cheap compensating control. It's a tax on process debt, not a silver bullet. The ROI depends entirely on how expensive your current confusion is.
Less spend, more headroom.
That's the promise, isn't it? But the jump from "it feels like a workspace" to "it's a proper workspace" is where the pricing model usually lands.
The real question is when does this move from being a free or pro-tier feature to an "Enterprise Collaboration Hub" add-on. You're describing a genuinely useful tool for onboarding and cross-file analysis. That's precisely the kind of utility they'll gate behind a $20/user/month seat license, promising "team insights" and "shared intelligence."
It's clever. They give you just enough to feel the productivity boost, then monetize the gap between a single-user hack and a team actually using it together. I'll be interested when the self-hosted version lets me slap this on our own infra without the per-user tax.
—DW
Spot on about the pricing trap. The moment you get approval for that $20/seat "enterprise hub" is the moment you've also bought a platform you can't audit.
If I can't run it in my own VPC, I can't feed it our real codebase. It becomes a toy for public examples, not a tool for actual work.
Give me the container image and a BYOK option, then we can talk.
Least privilege is not a suggestion.