Guides · Learn the operating loop

From first sign-in to accepted work, without losing the thread.

Follow the Matrix lifecycle by task and role. Every guide points back to the live app as the source of truth for your account, team and work.

YOUR PATHACCOUNT → EVIDENCE
01Enter02Connect03Run & steer04Accept
RESULTReal files, receipts and a flow you can reuse✓

Learn by the job you need to do.

Six compact playbooks cover onboarding, running work on a visible DAG, and acceptance. Start anywhere; the sequence stays visible.

01GET STARTED

Register and sign in

FOR · EVERYONE
  1. Open matrix.hicode.com.
  2. Create an account with your work email, or sign in.
  3. Your teams, Tasks and history follow the account, not one machine.
Create account ↗
02GET STARTED

Connect a Brain or a Hand

FOR · RESOURCE OWNER
  1. Install Matrix and sign in from the Matrix window; your browser completes the sign-in and binds the device.
  2. Confirm the CLIs it discovered; add a cloud API in Pool only if you need one. These are Brains.
  3. Bind a workspace folder to make this device a Hand. Confirm the device in Matrix under Settings › Devices.
Download a client →
03GET STARTED

Join a team

FOR · MEMBER
  1. Open the personal link from your team lead.
  2. Sign in or create an account.
  3. Use the company pool once an admin authorizes you; your private connections stay private.
How invitations work →
04RUN THE WORK

Start a Task

FOR · LEADER
  1. Describe the goal, then keep or choose the Device and Workspace.
  2. Pick the collaboration: a single agent, an AI Leader team, or manage it yourself.
  3. Pick the process: no flow, a saved static flow, or a dynamic plan the Leader proposes.
Open Matrix ↗
05RUN THE WORK

Watch and steer the run

FOR · LEADER
  1. Open the Task canvas: every node shows done, running, waiting or not started, with the reason.
  2. Stop, continue or retry a step; accept a runtime graph change after reading its diff.
  3. Drill into any call for its executor, inputs, outputs, artifacts and usage.
See DAG Flow →
06DELIVER

Accept with evidence

FOR · REVIEWER
  1. Check the files on the real workspace and the test results, not the summary.
  2. Compare receipts and artifacts with the acceptance condition.
  3. Treat missing or unverified evidence as incomplete, not successful.
Open Matrix ↗