BookSlash for Claude · AI

b/claude.
b/anthropic. b/projects.

Teams using Claude for engineering, writing, and analysis reach the same surfaces every day — the chat, the projects view, the Anthropic Console, the API keys. BookSlash gives each one a flat name your whole team types.

claude

resolved

Claude

claude.ai/chats

landed in 38ms

other shortcuts you might save

b/claudeb/claude-projectsb/anthropicb/claude-keys

Suggested slug patterns

Steal these. They work for most teams.

Battle-tested shortcut conventions for Claude, with notes on why each one survives the URL changes that break personal bookmarks.

  • b/claude

    Claude conversation home.

    The most-used AI URL on the team. Saving it as a slug ends the daily browser-history search.

    https://claude.ai/chats
  • b/claude-projects

    Claude Projects (workspaces with shared knowledge).

    Teams accumulate projects per use case; b/claude-projects is the team directory.

    https://claude.ai/projects
  • b/anthropic

    Anthropic Console (API + admin).

    Engineering reaches it for new keys, ops reaches it for billing, security reaches it for audit.

    https://console.anthropic.com
  • b/claude-keys

    Anthropic API keys page.

    Engineers reach it for every new project; saving the URL is faster than navigating the console.

    https://console.anthropic.com/settings/keys
  • b/claude-usage

    Usage and billing dashboard.

    Finance reaches it monthly; engineering managers track per-team cost from this URL.

    https://console.anthropic.com/settings/usage
  • b/claude-workbench

    Anthropic Workbench for prompt iteration.

    Engineers and PMs reach it for prompt design; saving the URL ends the navigation tax.

    https://console.anthropic.com/workbench

Common workflows

Three patterns that pay back in week one.

01

Engineering onboarding to the Anthropic workspace

New engineers receive b/anthropic, b/claude-keys, and b/claude-workbench on day one. They issue their first API key, run their first prompt, and reach the docs in five minutes.

02

Project-based knowledge sharing

Each team’s active Claude Projects live behind a slug pattern (b/claude-brand, b/claude-engineering). The slug reaches the same project across browsers; new project members find the workspace instantly.

03

Monthly cost review

b/claude-usage opens the per-key spend breakdown. Finance and engineering managers reach the same URL; the BookSlash audit log proves who pulled the numbers and when.

With and without

Same Claude. Different team experience.

Without shortcuts

Each engineer has private bookmarks for Claude and the Anthropic Console. Cost reviews start with "where is the usage URL?" New engineers wait for someone to share the project links.

With BookSlash

b/claude, b/anthropic, b/claude-keys, b/claude-projects, b/claude-usage. Five slugs cover the Anthropic surface for engineering, finance, and shared-knowledge work.

Frequently asked

BookSlash + Claude

No — slugs are URL → URL redirects. Claude handles the conversations on Anthropic infrastructure; BookSlash gets you to the right Claude page in one keystroke. The two systems never exchange data.

Claude Projects have URLs that respect Anthropic’s sharing rules. Point a slug at the project URL — the destination still requires a Claude login (or shared-project membership) to access.

Many teams use both. Namespace per provider: b/claude, b/chatgpt, b/perplexity. The b/ pattern stays consistent; switching tools is a one-edit slug update, not a re-bookmarking exercise for the whole team.

Yes — BookSlash ships a Raycast extension that resolves any b/* slug from the launcher. b/claude works the same in your browser as in Raycast.

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

BookSlash for Claude — Shortcuts to chats, projects, and the API console · BookSlash