resolved
ChatGPT
openai.com/
landed in 38msBookSlash for ChatGPT · AI
b/chatgpt.
b/gpts. b/openai.
Teams using ChatGPT and the OpenAI Platform reach the same handful of URLs daily — the active conversation, the custom GPT, the API keys, the usage dashboard. BookSlash gives each one a slug your whole team types.
chatgpt
other shortcuts you might save
b/chatgptb/gptsb/openaib/openai-keys
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for ChatGPT, with notes on why each one survives the URL changes that break personal bookmarks.
- b/chatgpt
ChatGPT main conversation surface.
Every team member opens it daily; saves the bookmark drift across browsers.
https://chat.openai.com - b/gpts
Custom GPTs the team has published.
Teams accumulate dozens of custom GPTs; the slug becomes the entry point to the team gallery.
https://chat.openai.com/gpts - b/openai
OpenAI Platform admin / API keys console.
Engineering reaches it for new keys, billing reaches it for usage, security reaches it for audit.
https://platform.openai.com - b/openai-keys
API keys management page.
Saves the URL from rotting in onboarding docs; engineers reach it for every new project.
https://platform.openai.com/api-keys - b/openai-usage
API usage and billing dashboard.
Finance and engineering managers reach it during monthly cost reviews.
https://platform.openai.com/usage - b/openai-playground
Prompt playground for testing.
Engineers and PMs both reach it for prompt iteration; saving the URL ends the daily-bookmark friction.
https://platform.openai.com/playground - b/openai-team
Team / workspace settings.
Admins reach it during member onboarding and audit.
https://platform.openai.com/settings/organization
Common workflows
Three patterns that pay back in week one.
01
Onboarding new engineers to the OpenAI workspace
Day-one engineers receive three slugs: b/openai, b/openai-keys, b/openai-playground. Replaces a 200-character "useful OpenAI URLs" Notion section. Engineers issue their first key, run their first prompt, and reach the docs without asking.
02
Cost review without dashboard archaeology
Finance and engineering managers reach b/openai-usage at the start of every month. The dashboard URL is buried; the slug is one keystroke. Pairs with b/openai-keys for the per-key breakdown.
03
Cross-team GPT discovery
b/gpts is the directory of every custom GPT the team has built. Marketing reaches the brand-voice GPT; engineering reaches the code-review GPT. The slug is the team’s shared catalogue.
With and without
Same ChatGPT. Different team experience.
Without shortcuts
Each engineer has private bookmarks for the OpenAI console. Finance pings engineering monthly for the usage URL. New engineers wait days for someone to share the team workspace link.
With BookSlash
b/chatgpt, b/openai, b/openai-keys, b/openai-usage. Four shortcuts cover the OpenAI surface for engineering, finance, and admin together.
Related integrations
Pair ChatGPT with one of these.
Frequently asked
BookSlash + ChatGPT
No — slugs are URL → URL redirects. ChatGPT handles the prompts; BookSlash gets you to the right ChatGPT page in one keystroke. The two systems never share data.
ChatGPT supports public conversation share links. Point a slug at the share URL (b/prompt-eng) and the slug works for anyone with the link. Internal-only conversations require a ChatGPT login at the destination.
Many teams use multiple AI tools. Namespace cleanly: b/chatgpt, b/claude, b/perplexity. The b/ pattern stays consistent across providers; the segment after disambiguates.
BookSlash analytics show per-slug click counts and per-user activity. ChatGPT itself owns the conversation-level data; BookSlash owns the routing-level data. Combined: you see who reaches which GPT and how often.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial