Public Hubs
Browse shared hub listings, starter prompts, audience guidance, and public connection paths.
Public hubs are shared hubs listed for discovery. They are useful for learning Thalovant, trying examples, and creating Free-path connections before creating your own hubs.
You can use a public hub without owning that hub. The shared hub keeps its own skills and runtime. You create your own connection and keep that client’s access rules narrow.
Find Showroom and Explore
Section titled “Find Showroom and Explore”Open Showroom to try Thalovant’s public demonstrations, or Explore to browse public hubs. Their public overview pages can be found by search engines and opened without signing in. Search results and updates depend on each search engine’s crawl schedule.
Public discovery does not publish your workspace. Private hubs, conversations, memory, analytics, billing, and connection details remain behind account access. Sign in to create a connection or manage your own resources. Publishing a hub listing requires the review described in List Your Own Hub.
Daily Desk is the public showroom for the private Daily Desk path. It keeps a short chat memory for each connected client, so it can answer “what was the last joke you told me?”, and forgets it when you say “forget what I said”. The web preview on the site keeps none, and it never reads private workspace data. Use Memory when you want a paid private workspace to remember preferences, notes, and facts.
For quick date and time checks, try prompts such as:
- “What time is it?” for the hub’s current location;
- “What time is it in Charlottetown?” for a named city or time zone;
- “What date is it today?” for the current calendar date.
Daily Desk answers recognized world-time locations directly. If it can’t resolve an explicitly named location, it asks for a clearer city or time zone instead of silently answering for the hub’s default location.
For the full route, see the public hub scenario. For the simplest account path, see Free Tier.
If you’re brand new, public hubs are the safest first path because you can learn the client and access rules flow without creating your own hub.
Public Hub Cards
Section titled “Public Hub Cards”Public hub listings can include:
- title and description;
- quality label;
- community label;
- audience category;
- age guidance;
- tags;
- starter prompts.
Starter Prompts
Section titled “Starter Prompts”Starter prompts show what the hub is designed to handle. You can copy a prompt or try it when live preview is available for that hub and your plan has remaining preview allowance.
Good starter prompts are:
- short;
- plain language;
- free of links or markup;
- clearly related to the hub purpose.
Public Hub Client Path
Section titled “Public Hub Client Path”- Choose a public hub. Use filters for quality label, audience, age guidance, and tags.
- Read the listing. Check the description, audience, starter prompts, and any quality label.
- Create a connection. The client connects to the chosen public hub.
- Use narrow access. Public hub clients are designed for safe question-style access first.
- Review Billing when you need more. Move toward the workspace path when you need private hubs, more connections, separate skills, or runtime config.
Stop after one public hub connection and confirm the client exists with narrow access rules. That first pass teaches the same pattern you’ll use for owned hubs later.
Public Preview and Signup
Section titled “Public Preview and Signup”Some public hubs let you try a browser preview before creating a connection. Start with a starter prompt, then create an account only when you want the hub saved to your own flow.
Preview is available only while the hub is active, public, and its preview status is ready. A recent visibility or hub update can briefly show preview as refreshing. If preview remains unavailable, use the normal connection path or check the hub status instead of repeatedly submitting the prompt.
A preview problem doesn’t change whether a hub is public or private. If browser preview is unavailable, try your normal client connection and check the hub’s status.
If a public hub link sends you to account creation, finish Sign In and Account Access and return to the same hub. The selected public hub should stay attached to the signup path.
API Example Links
Section titled “API Example Links”Some public hub listings may include a simple API example for developers. Treat it as a learning example, not as a secret-bearing setup path.
If the example needs private setup material, create a connection first and keep setup links, connection files, and copied commands private.
Public Hub vs Owned Hub
Section titled “Public Hub vs Owned Hub”| Choice | You manage | Good for |
|---|---|---|
| Public hub | Your connection and access rules. | Learning, trying examples, and Free-path exploration without personal memory. |
| Owned hub | Hub, skills, runtime config, clients, memory, and access rules. | Private workspace experiences and team-controlled setup. |
List Your Own Hub
Section titled “List Your Own Hub”Only reviewed hubs appear in the public catalogue. Every public hub, on every plan, passes a Thalovant review before it is listed.
When you make a hub public, its listing status becomes pending. An approved hub appears in the catalogue. A rejected hub stays unlisted and shows the review note. Listing needs a Work plan with listing room; see Publish a Public Hub.
Public Hub Setup Looks Right When
Section titled “Public Hub Setup Looks Right When”A public hub setup looks right when:
- the listing explains what the hub is for;
- audience and age guidance fit your use;
- the client name explains the purpose;
- access rules are narrow;
- Dashboard shows no unexpected attention item.