What you will finish
This quickstart is the first truthful developer path through MinuteWork.
By the end, you will have:
- created or selected a Server
- scaffolded a local workspace
- authenticated and linked the repo
- run the local validation and preview loop
- identified the session-broker lane as an alternate next step
Step 1: Create or select a Server
- 01
Sign in to MinuteWork
Start from the hosted product surface and authenticate with your platform account.
- 02
Create or choose a Server
If you already belong to a Server, use it. Otherwise create one and finish the onboarding flow so the private runtime boundary exists before you link a local workspace.
- 03
Confirm the Server is your private workspace
Keep the mental model straight from the start: the Server is the private operating space where agents, payloads, memory, workflows, and installed capabilities live by default.
Step 2: Scaffold the local workspace
If you have not set up the CLI yet, read the CLI guide first. Otherwise create a workspace from an empty directory:
minutework init my-server --starter tenant-app
cd my-serverStart with tenant-app unless you already know you need Python runtime work
such as webhooks, jobs, ingestion, or long-running compute.
Step 3: Authenticate and link the repo
Connect the local repo to the right platform account and target environment:
minutework login
minutework link
minutework env use previewThis gives the repo an explicit tenant and environment binding without writing plaintext secrets into the committed source tree.
Step 4: Run the local loop
Once the workspace is linked, run the local workflow:
minutework validate
minutework sandbox status
minutework dev
minutework testWhat these commands tell you:
validatechecks the selected authoring inputsandbox statusshows whether the local preview and test plan is readydevrefreshes local artifacts and launches the enabled preview surfacestestrefreshes compile and codegen state before running starter-local tests
Step 5: Choose your next track
At this point you have the right foundation. The next step depends on what you want to build.
Understand the Server model
Learn the core product term that defines the private runtime boundary you just linked the workspace to.
Try the session broker lane
See the current CLI surface in more detail, including the developer-local broker flow for human or Claude-backed coding sessions.
Decide what stays private
Understand when something belongs in the private runtime, the public release surface, or both.
Model public content
If you want docs, marketing pages, or public reference content, start with the public-site snapshot contract.