# Grok Bot Public template publish fails with "A team must be selected to share a team template" on personal Ultra

**URL:** <https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [September 7, 2026, 4:20pm UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926 "2026-09-07T16:20:26Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![idan\_lin](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@idan\_lin](https://forum.cursor.com/u/idan_lin)\
**Post date:** [September 7, 2026, 4:20pm UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/1 "2026-09-07T16:20:26Z")

</div>

### Where does the bug appear (feature/product)?

Grok Bot

### Describe the Bug

On a **personal Cursor Ultra** account (not Cursor Teams), asking a Bot to create a **Public** shareable template fails every time.

The export tool / account guidance says this account can **only create PUBLIC** templates (do not ask about TEAM). We pass `visibility: "public"`.

The server still returns:

```auto
Error: [failed_precondition] A team must be selected to share a team template.

```

No review/publish card appears, so no `https://x.ai/bot/<id>` link is created and nobody can **Add to Grok Bot**.

Personal Ultra dashboard has no “Public template sharing” toggle (that control is documented for Teams/Enterprise admins). In-app Send Feedback was also submitted earlier for the same issue. Related public note: [Idan Lin on X: "Tried to publish a Public Grok Bot template on personal Cursor Ultra. Tooling says this account can only create Public templates. Server returns: "A team must be selected to share a team template." No review card, no https://t.co/cZBvFeehoK link — so nobody can Add it. Share as te… / X](https://x.com/eddiearc6/status/2096654499838673322)

This looks like Public export is incorrectly routed through the **team-template** path.

### Steps to Reproduce

1. Sign in with personal Cursor Ultra (no Team).
2. Open any Bot → ask it to create / share a Public template (`create_bot_share_json` with `visibility: "public"`).
3. Observe the failed\_precondition error above; no review card / no x.ai/bot link.

### Expected Behavior

Public template export succeeds (or clearly fails with a documented personal-account limitation). If Public is supported for Ultra, a review card and `x.ai/bot` link should appear. If not supported, hide Share-as-template / do not document Public-only for this account.

### Operating System

MacOS

### Version Information

Grok Bot latest stable as of 2026-09-07; Cursor Ultra individual

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://forum.cursor.com/u/discourse_ai_spam)\
**Post date:** [September 7, 2026, 4:20pm UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/2 "2026-09-07T16:20:31Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [September 7, 2026, 4:52pm UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/6 "2026-09-07T16:52:08Z")

</div>



---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [September 8, 2026, 8:21am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/9 "2026-09-08T08:21:35Z")

</div>

Hey @idan_lin thanks for the detailed report. This isn’t something you misconfigured, and it isn’t intended behavior. A Public template export shouldn’t need a team at all, but right now the export flow trips up when your account is still attached to more than one team workspace, even on a personal Ultra plan (an account can stay attached to leftover workspaces from old invite links, trials, or canceled self-serve teams that have no seats or subscription).

Workaround: open [cursor.com/dashboard](http://cursor.com/dashboard) and leave any team workspaces your account is still part of. Once it isn’t attached to more than one, ask the Bot to share itself as a Public template again and the review card + x.ai/bot link should appear.

If you’d rather stay in those workspaces, there’s no in-app way around it today, so I’d sit tight. We’ve let the team know and this is an issue we’re tracking, and I’ll follow up here once it’s sorted.

---

<div class="post-metadata">

**Author:** ![idan\_lin](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@idan\_lin](https://forum.cursor.com/u/idan_lin)\
**Post date:** [September 8, 2026, 9:41am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/10 "2026-09-08T09:41:16Z")

</div>

Thanks Mohit — that matches what I saw.

I checked [https://cursor.com/dashboard](https://cursor.com/dashboard) on personal Ultra (idan lin). There’s no leftover Cursor team/workspace to leave: no team switcher, and Members shows “Upgrade to Teams” / “Create team” only. GitHub orgs (AIsa-team / eddiearc) show up under integrations, but those aren’t Cursor teams.

I retried Public template share after that and still get:

`[failed_precondition] A team must be selected to share a team template.`

Happy to retest again if there’s another place leftover teams hide, or if you want screenshots of the dashboard / the exact share error.

 ![shot-call_yzwQuAirdtrnzjPvc49ePrBDfc_093479e89d0db40d](https://us1.discourse-cdn.com/cursor1/original/3X/e/1/e1854098b406fef4daedbc8cca1caf32b601b7fb.png)

 ![shot-call_Qbp0zwkxgXTB6y6c0MtvfUdBfc_0fbdc1328cb2c736](https://us1.discourse-cdn.com/cursor1/original/3X/3/2/324c30b470759aa9821adcd2c514cf02812e832a.png)

 ![shot-call_99iT0PIzesi71RckuklL9ByDfc_0fbdc1328cb2c736](https://us1.discourse-cdn.com/cursor1/original/3X/a/b/ab2a0184164898ca710668eee34a527715f15918.png)

---

<div class="post-metadata">

**Author:** ![idan\_lin](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@idan\_lin](https://forum.cursor.com/u/idan_lin)\
**Post date:** [September 8, 2026, 6:08pm UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/11 "2026-09-08T18:08:53Z")

</div>

@mohitjain following up — this is blocking my work and I need Public template share ASAP.

Cursor support ([hi@cursor.com](mailto:hi@cursor.com) / T-F60004) just checked [eddiearc6@gmail.com](mailto:eddiearc6@gmail.com): personal Ultra with **no team or workspace memberships attached** , so nothing to leave/remove. That matches what my dashboard shows.

I retried Public share again after that and still get:  
`[failed_precondition] A team must be selected to share a team template.`

So the leftover-team workaround doesn’t apply here. Can you escalate / prioritize the product fix, or tell me any other path to get a usable `x.ai/bot` Add link on personal Ultra?

---

<div class="post-metadata">

**Author:** ![idan\_lin](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@idan\_lin](https://forum.cursor.com/u/idan_lin)\
**Post date:** [September 11, 2026, 6:09am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/12 "2026-09-11T06:09:24Z")

</div>

Still blocked as of 2026-09-11 (Shanghai).

Personal Ultra. `create_bot_share_json` with visibility=public still returns:  
`[failed_precondition] A team must be selected to share a team template.`

No leftover team workspaces on dashboard (Sam at [hi@cursor.com](mailto:hi@cursor.com) already confirmed no team/workspace memberships on T-F60004 / T-F49035 and closed that thread).

This is blocking my work — I need a working Public template / Add link on personal Ultra. @mohitjain can engineering please reopen or escalate? Happy to provide another screenshot or a live share attempt.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [September 11, 2026, 6:55am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/13 "2026-09-11T06:55:42Z")

</div>

@idan_lin you’re right, there’s nothing on your side to leave. Those are old 0-seat self-serve team memberships that don’t show in your dashboard or a standard account check, but the backend still counts them, which is what trips the Public publish. Please email [hi@cursor.com](mailto:hi@cursor.com) from your account address and ask them to remove your leftover backend team memberships. Public export should work once they’re cleared.

---

<div class="post-metadata">

**Author:** ![idan\_lin](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@idan\_lin](https://forum.cursor.com/u/idan_lin)\
**Post date:** [October 10, 2026, 2:51am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/14 "2026-10-10T02:51:14Z")

</div>

Following up on this — still blocked on personal Ultra (`eddiearc6@gmail.com`).

On 2026-09-11 I emailed hi@ as Mohit suggested. Support (Sam) said they **cannot** clear leftover 0-seat backend team memberships from the support side, that the issue is with the product team, and closed the ticket (`T-F49035` / `T-F60004`).

I just sent another follow-up to hi@ today (2026-10-10) asking for product status / ETA / workaround. Public template share still fails with “A team must be selected to share a team template.”

Any update from the product side on clearing those residual rows for personal Ultra accounts?

---

<div class="post-metadata">

**Author:** ![Shagghie\_Superstar](https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/32.png) [@Shagghie\_Superstar](https://forum.cursor.com/u/Shagghie_Superstar)\
**Post date:** [October 15, 2026, 4:56am UTC](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926/15 "2026-10-15T04:56:25Z")

</div>

Same issue here. Adding my details in case it helps the team prioritize.

I’m on Ultra on a personal account, but it’s still attached to a canceled legacy team (“Shagghie’s Team”, 0 seats) that I never set up on purpose and can’t leave. Every Grok Bot template share fails with `[failed_precondition] A team must be selected to share a team template.` It happens with both public and team visibility, from the personal account, after switching contexts, and after re-logging with X. Trying “Enable Grok Bot” on the legacy team also fails with “Couldn’t enable Grok Bot. Try again.” The same bot shared fine as public until late September.

Support confirmed it’s the known leftover-team bug and passed it to a teammate. My ticket is **T-H44914**.

This matters a lot for me because I’m in the Grok Bot Creator Rewards pilot, and right now I can’t publish or update any template. I have a new version of my Hermes Fleet Ops template ready, and I’m submitting a companion plugin (Hermes Fleet Management) that’s meant to ship with it. Both are blocked until the team is detached, and I don’t want to lose creator status over a backend issue I can’t fix myself.

If staff can bump T-H44914, I’m happy to test the fix right away. Thanks!

— @pixelrainbownft
