Hey @Miguel,
This is one of those fun edge cases where legacy behavior and new workflows collide. In short:
There is no
spoonmain
.
Well… it exists, but not always in the way you expect!
What’s going on?
- Every project starts with a
main
model by default — but:- It might not appear in the UI or
GetModels()
results. - It exists only as an ID, not a name.
- If you try to create it again, the API will block you — because it’s already there (even if you can’t see it).
- It might not appear in the UI or
This happens because V2 connectors and older legacy patterns defaulted to main
.
The philosophy of V3 (next-gen) connectors is: pick or define your trunk yourself.
So what should you do?
- Don’t assume
main
exists or is discoverable. - Instead, when you create a project, create a model with a clear name (e.g.,
production
,design
,baseline
) and push to that. - If you’re inheriting projects from V2-land and
main
appears invisible:- Look for a model with an empty
name
— that’s your ghostmain
.
- Look for a model with an empty
TLDR:
“There is no
main
. Define your trunk. Create what makes sense for your workflow.”