Getting More Help

You have four places to turn, depending on what you need: interactive lessons (/tutorial), bug and feature reports (/hq-bug), the rest of this knowledge base, and, sometimes, a different tool entirely. This article covers when to use each.

Learn by doing: /tutorial#

The fastest way to build confidence is not reading, it's a guided rep with your own HQ. Run:

/tutorial

You'll get a menu of ten hands-on lessons, each following the same rhythm: a short concept, a live demonstration in your actual HQ, an exercise you do yourself, and a check that it worked. The topics:

1. Cloud & Team Collaboration, signing in, sync, sharing, and secrets for teams.
2. Ralph Principles, the working mindset behind HQ: one task at a time, verified before moving on.
3. Working with HQ, the daily workflow and how the folders fit together.
4. Knowledge Architecture, where knowledge lives and how HQ finds it.
5. Session Hygiene, why fresh sessions beat marathon ones, and the handoff habit.
6. Context Management, keeping the AI's working memory focused.
7. Projects, turning ideas into planned, trackable work with PRDs.
8. Scaling, running work in parallel across multiple sessions.
9. The Ralph Loop, autonomous orchestration: HQ working through a project on its own.
10. Workers, creating persistent AI specialists for a domain.

You can jump straight to a topic, e.g. /tutorial sessions or /tutorial workers. The menu also adapts to your HQ, if you're on a team with cloud enabled, it recommends the collaboration lesson first.

Report a problem or request a feature: /hq-bug#

When something is broken, confusing, or missing, tell the team directly from your session:

/hq-bug the sync app never appeared after install
/hq-bug feature let me schedule a weekly report

1. Type /hq-bug followed by a one-line description. Start with feature if it's a request rather than a bug (bug is the default).
2. HQ assembles the report and automatically attaches your session context, what you were doing, in which environment, so you don't have to write a detailed reproduction.
3. Confirm, and it's submitted. No screenshots, no forms.

Don't self-censor: "this was confusing" is a valid report, and it's exactly the kind that improves HQ for the next person. If you're not sure whether something is a bug or your own mistake, report it anyway, the context attachment lets the team figure that out.

When HQ is not the right tool#

HQ shines at a specific kind of work. Knowing its sweet spot saves you frustration:

• Quick one-off questions ("What's the capital of Peru?", "Rewrite this sentence"), just use a plain chat with Claude or ChatGPT. Spinning up an HQ session adds ceremony with no payoff, because nothing about the answer needs your company's context or deserves to be remembered.
• Real-time team conversation, use Slack (or your team chat). HQ's /dm sends notifications and can hand a teammate a ready-to-run prompt, but it's for passing work between people, not back-and-forth chatting.
• HQ's sweet spot: repeatable work where knowledge compounds. Weekly reports, customer research, project planning, content in your brand voice, anything you'll do more than once, anything a teammate should benefit from. The first time you do it in HQ, you're teaching it; every time after, it's faster, because what you teach it sticks.

A useful test: "Will I, or a teammate, ever want the context from this again?" If yes, do it in HQ. If no, plain chat is fine.

Find your own answer in this knowledge base#

The full index is in the README. The pages people need most often:

• Something's broken → The "I'm Stuck" Guide
• Quick answers → FAQ
• Just installed, what now → Your First Win
• What does this word mean → Glossary
• Sync or sharing trouble → Sync Guide and Sharing Your Work

And /search inside HQ searches your own knowledge, policies, and projects, often the answer to "how do we do X?" is already written down in your company's files. See Finding Anything.

Common questions#

If you get stuck#

If you're here because something is broken, The "I'm Stuck" Guide is organized by symptom and covers the most common failures. If it doesn't, /hq-bug with one honest sentence is always the right move.