Unstick your first week in Auxot

Name the five dead-ends new people actually hit (empty chat, blocked app, silent Slack, red System Health, wrong API key shape) so you know which tutorial to open instead of thrashing.

Plus: three Admin Agent prompts that turn 'something is wrong' into a one-page triage note you can paste to your admin or your future self.

Audience	Everyone · Admins
Time	~7 min
Prerequisites	You can sign in to Auxot. Helpful: you already said hello once ([Say hello to the Admin Agent](/tutorials/say-hello-to-admin-agent)) and you know where System Health lives ([Take Auxot's pulse in 10 seconds](/tutorials/take-auxots-pulse)).
You'll end up with	A mental map of the first-week failure modes, which screen each one points at, and the next tutorial or setting to open. No new features required: pattern recognition only.

When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.

Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.

Why this matters

New software always feels broken the first time. Auxot is no exception. The failure modes are boring and repeatable, which is good news: once you recognize the pattern, you stop inventing a new panic every time.

The five gotchas below are the ones that generate real support noise. They are not bugs in the sense of random defects. They are gates: onboarding that is not finished yet, identity that is not linked yet, models that are not wired yet, infrastructure that is not healthy yet, or keys that do not match how you actually work.

Today you learn the map. The next time something feels off, you skip the panic and open the right Settings page directly.

Nothing here replaces your admin’s judgment on billing or security. It gives you language for what you are seeing so you can move.

Quick start

Sign in: open Auxot in your browser and log in.
Open Chat: click Chat in the left menu. If the agent picker is empty or replies never start, treat that as Gotcha A (see Walkthrough).
Try /app: if you land on onboarding or onboarding-blocked instead of the normal shell, that is Gotcha B (owner flow vs teammate wait).
Open System Health: click System Health in the left menu. Anything not green is Gotcha C (read the card before you assume the model is broken when actually a card on System Health is yellow).
Skim Settings paths you will need this week: Settings → Linked Accounts for chat identity (Link your chat apps to your Auxot account), Settings → API Keys for programmatic access (Generate your first API key), and (if you touch automation) the personal vs team key story (Pick personal or team API keys for real work).

Done? You can name which of the five gotchas matches what you saw, and you know the next page or tutorial to open.

The agent can do that?

You do not have to self-diagnose alone. Paste symptoms into the Admin Agent and let it sort which bucket you are in.

1. Turn a vague “it does not work” into a checklist

I am new to Auxot. Symptom in one sentence: [paste]. List which of these buckets fits: (A) empty chat / no model, (B) forced onboarding or onboarding-blocked, (C) Slack or Discord bot ignores me or only reacts with 🙈, (D) System Health not all green, (E) API key prefix or scope confusion. For each possible bucket, name the exact Settings or left-menu page I should open next and one concrete thing to verify there. Stop after the checklist.

Why it’s non-obvious: “Broken” sounds like one problem. It is usually one of a small set of gates. The Admin Agent forces the split so you do not treat a Linked Accounts gap like a model outage.

2. Draft a polite note to your admin (when you are blocked on someone else)

Draft a short message I can send my org owner. Fact: I hit onboarding-blocked / cannot finish a step / Slack still anonymous after I tried linking. Tone: neutral, no blame, asks for one specific action or ETA. Under 120 words.

Why it’s non-obvious: Blocked teammates often go quiet rather than escalate. A neutral note moves the owner without shaming them.

3. Capture a “first week done” snapshot for yourself

Assume I am at the end of week one. Based only on what a normal Auxot account should have touched (chat, System Health, one provider or key path, optional Slack link), give me a five-bullet self-audit I can save in notes. Each bullet: what should be true, how I would prove it in the UI in under twenty seconds.

Why it’s non-obvious: Week one blur makes people forget what they already fixed. A saved snapshot prevents re-opening the same investigation on day eight.

Go deeper

Gotcha A: Chat feels empty or models never answer

Symptoms: you open Chat, pick an agent, type, and nothing streams. Or the picker has no sensible model path.

What it usually means: there is not a working model route yet for what you are trying to do. Admins fix this under provider and model settings (Connect a cloud AI model is the common first path).

If you are not an admin, you still benefit from knowing the vocabulary: screenshot what you see, send it to whoever runs providers, and point them at that tutorial.

Gotcha B: `/app` keeps bouncing you to onboarding or onboarding-blocked

Symptoms: you never reach the normal shell. Owners see the welcome wizard. Non-owners see a blocked page until the owner finishes.

What it usually means: the organization is still in first-run registration, not a mystery bug. Owners follow Finish first-run onboarding. Invitees who arrived through email start from Accept your invitation and join your organization.

Gotcha C: System Health shows something other than “all clear”

Symptoms: a card is offline, degraded, or throwing an error string you do not love.

What it usually means: something in the stack (database, cache, provider auth, integration token) needs attention. The page is the honest surface. Use Take Auxot’s pulse in 10 seconds for how to read it, then follow the card’s own helper text before you open a ticket.

Gotcha D: Slack or Discord “does not see me”

Symptoms: bots stay quiet, or you only see 🙈 on mentions-only channels, or tools refuse because the human is ambiguous.

What it usually means: Linked Accounts is not finished for your user, even if an admin already connected the workspace. Do Link your chat apps to your Auxot account before you debug agent prompts.

Gotcha E: API keys work in the browser lab but fail in scripts, CI, or intakes

Symptoms: 401, wrong org scope, or teammates sharing a personal key by accident.

What it usually means: the prefix and audience of the key (user. vs team.) does not match the automation. Read Pick personal or team API keys for real work. If you never generated one, start at Generate your first API key.

Walkthrough

Step 1: Confirm you are in the right org

Look at the org switcher or profile corner (exact label varies by skin). If you expected a different workspace, stop and switch before you debug “missing agents.”

Step 2: Walk the five gotchas in order

Walk the Quick start list above in order. Most people who feel lost are stuck on B or D, not on unusual agent logic.

Step 3: Write down what you fixed

One line per day is enough: Linked Slack, owner finished billing step, rotated bad API key. Future-you reads like a human instead of guessing from memory.

What’s next

→ Finish first-run onboarding. If you are the owner and the app will not let you past registration.
→ Accept your invitation and join your organization. If you arrived on an invite and still feel blocked.
→ Connect a cloud AI model. When Chat is empty because no cloud model is connected yet (admins).
→ Link your chat apps to your Auxot account. When Slack or Discord cannot tell which Auxot user is at the keyboard.
→ Take Auxot’s pulse in 10 seconds. When you want a daily ten-second habit after the map makes sense.
→ Find the right screen for your next question. When you are past the gates but the left menu still feels like guesswork.
→ Make your first hour in Auxot count. When you want a deliberate first working session after the map makes sense.

Reference

Left menu anchors: Chat, System Health, Settings (profile and org configuration live here).
Invite flow: Invite your first teammate (admin side).
See also: Say hello to the Admin Agent, Pick personal or team API keys for real work, Find the right screen for your next question, Onboard a new teammate to your agents