Auxot
Tutorials Docs Pricing Login

Choose your day-two track in Auxot

Stop reopening every menu on day two. Pick one track (context, workflow, Slack, or a specialist agent), finish a single **Quick start** through its **Done?** line, and defer the other tracks on purpose for the rest of the week.

Plus: three Admin Agent debates that force a single day-two track so **Context Files**, **Workflows**, **Slack**, and custom agents stop competing for the same calendar block.

Audience Everyone · Admins
Time ~6 min
Prerequisites You already survived day one in the shell ([Make your first hour in Auxot count](/tutorials/make-your-first-hour-in-auxot-count)) or you can at least name each left-menu area ([Find the right screen for your next question](/tutorials/find-the-right-screen-for-your-next-question)). Helpful: [Unstick your first week in Auxot](/tutorials/unstick-your-first-week-in-auxot) if something still felt fuzzy.
You'll end up with One declared track with a first milestone you can finish today, a written skip list for the other tracks this week, and three Admin Agent prompts that re-run the fork when your role or calendar changes.

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

Day one is about proof: health, Chat, maybe providers, maybe one context file, maybe Audit Logs. Day two is where people try to do everything and finish nothing. Four honest tracks compete for the same afternoon: deepen Context Files, ship a first Workflow, wire Slack so humans stop looking anonymous, or build a second persona in Settings → Agents that is not the Admin Agent.

Each track is legitimate. The failure mode is starting all four before lunch.

This tutorial does not pick for you. It forces a public choice, a small first win inside that choice, and language for what you are not doing yet.

Today, you name the track and finish one Quick start through its Done? line. The next time you open Auxot, you extend the same track in a second session instead of clicking around the menu again.

If you are not an admin, some tracks need a ping instead of a click. The prompts below spell that out so you do not confuse missing permissions with missing talent.

Quick start

  1. Inventory day one honestly: in Chat → Admin Agent, paste the prompt from The agent can do that? → 1 below, or write five bullets yourself: what you finished, what you skipped, what hurt.
  2. Glance at agents: open Settings → Agents and count how many non-Admin personas you already have. Zero is fine. It just changes how greedy the specialist agent track should be this week.
  3. Pick one track only: Context (more files), Workflow (first automation), Slack (people in channels), or Specialist agent (a new agent row beyond the Admin Agent). Say the name out loud like a commitment device.
  4. Open exactly one matching tutorial: work only inside that file’s Quick start through its Done? line today: Add your first context file, Run a workflow, Connect Slack to your agents, or Create an agent from scratch. Stop when you hit Done?, even if the walkthrough tempts you.
  5. Write the skip list: in your notes, finish this sentence four times: This week I am not starting ____ because I chose ____. Use the three tracks you did not pick.

Done? You can read your skip list aloud without wincing, and the tutorial you opened shows a checked Done? state for today.

The agent can do that?

These prompts ask the Admin Agent to argue for a single track instead of letting you start four. Paste in Chat → Admin Agent.

1. Force a single day-two track

Here is what I finished on day one and what still feels messy: [paste five bullets]. I can spend forty-five focused minutes today. Pick exactly one day-two track for me: Context Files depth, first Workflow, Slack wiring for humans in channels, or building a new specialist agent beyond the Admin Agent. Defend in five bullets, name what I should deliberately skip this week, and call out if I need an admin instead of more clicking.

Why it’s non-obvious: Left alone, people rank tracks by anxiety instead of leverage. A forced pick surfaces skip on purpose language you can send to your team, not just a private todo list.

2. Shrink the chosen track to a ten-minute first win

I committed to day-two track: [Context / Workflow / Slack / Specialist agent]. List three milestones inside that track ordered smallest to largest. Circle only the first milestone that fits in ten minutes after I already read the tutorial Quick start. Tell me exactly which left-menu labels I should click for that ten-minute slice.

Why it’s non-obvious: Tutorial Quick start sections already hold the smallest first win. You want the Admin Agent to align with those steps instead of inventing a separate plan.

3. Draft the admin ping if permissions block the track

I picked track [name] but I lack access to [Providers / Users / Slack install / etc.]. Draft a four-sentence DM to my Auxot org admin: neutral tone, names the blocker, points at the relevant Settings path, and proposes one calendar-friendly fix. No blame, no jargon soup.

Why it’s non-obvious: Members who cannot get unstuck often stop using Auxot rather than ask for help. A short DM moves the org forward while you spend your forty-five minutes on something else useful.

Go deeper

When Discord should win instead of Slack

If your company actually coordinates in Discord, swap the chat track to Connect Discord to your agents instead of the Slack tutorial. The day-two discipline is the same: one integration surface gets your forty-five minutes, not both.

When API keys or MCP should wait until day three

If nothing external calls Auxot yet, defer Generate your first API key and Add an MCP server until a workflow or agent actually needs them. Keys without a caller are just credentials you will have to rotate later for no reason.

When the specialist track should be job description polish instead of a new row

If you already have an agent that feels close but bland, spend day two inside Give your agent its job description before you create another agent shell. New rows are not free for teammates who browse Settings → Agents.

Walkthrough

Step 1: Write the honest inventory

Open Chat → Admin Agent and run prompt 1 from above, or write the five bullets yourself if you prefer not to paste. You are collecting facts, not impressions.

Step 2: Look at agents without building yet

Open Settings → Agents. Scroll once. If the list is only the Admin Agent, the specialist track is allowed to mean first custom agent. If the list is long, the specialist track might mean tighten one existing agent instead (see Go deeper).

Step 3: Pick the track and say it twice

Say the track name out loud, then type it into your notes app as the title of a calendar event. If you cannot say it without adding and also, you are still multi-tracking. Split also into next week.

Step 4: Execute only the Quick start through Done

Open the single tutorial you picked. Follow Quick start until the line that starts with Done? and satisfies it. Close the tab. Resist the walkthrough until your next session.

Step 5: Publish the skip list somewhere durable

Paste your four not starting sentences into whatever your team already reads (Slack pin, internal doc, ticket comment). Future-you should not have to renegotiate the fork alone again on day five.

What’s next

Reference

Browse all tutorials