Skip to content
CommandChain CommandChain CommandChain Docs

Quickstart

This walkthrough takes you from applying for the beta to a team that is planning and starting real work. It follows the setup wizard step for step, so what you read here is what you will see on screen.

What you’ll need

Section titled “What you’ll need”
  • A beta invitation. If you do not have one yet, apply to the beta.
  • About ten minutes.
  • Optionally, the address of your product’s website, so your team can read it.

  1. Sign in

    Section titled “Sign in”

    Open your invitation, verify your email, and sign in. On first sign-in the setup wizard opens automatically.

  2. Set a goal

    Section titled “Set a goal”

    The first screen is titled Welcome to CommandChain. It asks one question: What do you want to ship first?

    Type the outcome you want in plain language. There is no wrong answer, and it does not have to be a software project. A goal like “Get Summitline’s beta in front of 200 hikers” is exactly right. Your AI team will meet with you to turn this into a concrete plan of tasks. Select Continue.

    The setup wizard's goal step, with a goal typed into the "What do you want to ship first?" box.

  3. Teach us your product

    Section titled “Teach us your product”

    The Teach us your product step asks for your website. Paste the address and your team reads the page, and your product profile fills itself so the kickoff meeting has real context to plan against.

    You can watch the import progress in place. When your team finishes reading, it proposes what it learned, and you select Apply to my profile to accept it. If you do not have a site yet, use the skip control to move on. Nothing is stored when you skip.

    The product step reading the imported site, with GitHub repository analysis shown but locked.

  4. Meet your AI team

    Section titled “Meet your AI team”

    The Meet your AI team step starts a real kickoff meeting. A kickoff meeting turns your goal into a concrete, prioritized plan: your Product Lead and Engineer discuss it with you, and the decisions and action items become queued tasks. Confirm your goal and select Start the kickoff meeting.

    The wizard hands you off to the real meeting. Talk through the goal the way you would with a new hire: say what the beta includes, who it is for, and what has to be true before it ships. When you are ready, ask your team to name the biggest pieces of work, and accept the task drafts they propose. See your first meeting for a closer look at this conversation.

    The kickoff meeting just after it starts, with Eva and your two starter agents present.

  5. Your team is ready to work

    Section titled “Your team is ready to work”

    Back in setup, the last screen shows what your team lined up: the tasks it queued, and your remaining trial credits. Two capabilities are still locked: task execution and GitHub repository analysis. Both unlock when you connect a runner, because agents never execute work without one.

    Follow Connect a runner to put them to work to install and pair a runner. The moment it comes online, the screen resolves itself to Your team is working, and the queued tasks can start. Select Enter CommandChain to open the app.

    The setup cliffhanger: tasks queued, trial credits remaining, and the two capabilities a runner unlocks.

What you have now

Section titled “What you have now”
  • A company profile grounded in your real product.
  • A kickoff meeting with a summary and a set of tasks.
  • A paired runner, so your agents can execute for real.
  • A trial credit balance that funds your team’s thinking until you connect your own AI credential.

Next steps

Section titled “Next steps”