Skip to content
HandbookGetting started

Your first project: from a workspace to an invitation page

Prepare your account and runtime, choose an Agent and model, create an invitation page, and check the actual file.

10 min read

What you will be able to do

Complete a task independently, then find, open, and check your webpage in the workspace.

You do not need to learn to code before getting started. We will use a fictional “Weekend Walking Club” to practice turning instructions into a file you can open. The result is weekend-walk/index.html: a webpage containing text, styling, and a button. It stays in your workspace initially. You can decide later whether to share it publicly.

From an idea to a result you can check
  1. Describe the taskGoal, materials, constraints
  2. Let the Agent workWatch steps and answer questions
  3. Open the saved resultFind the actual project file
  4. Check and improveTry it, then give precise feedback
A finished reply is a starting point for checking the work.

The diagram follows four steps: explain the task, let the Agent work, open the saved result, then check and improve it. Read the invitation page and try its button; any issue you find becomes a specific request for the next turn.

1. Prepare your account and working environment

Open Macshop in another tab and keep this guide alongside it. Sign in if you already have an account. Otherwise choose “Continue with Google” or create an account with your email. Email registration asks you to create and confirm a password, then enter the verification code you receive. If it does not arrive, check the address and spam folder, then try again when “Resend verification code” becomes available. Follow the initial setup prompts.

You also need access to usage for the selected model. Check the product's usage screen or model notice for your current options; the scope and expiration of plans, credits, and grants are shown there. A free cloud computer does not mean every model call is free. See Models and usage for the distinctions.

For this exercise, use “Cloud computer.” You do not need local development software, a domain, or a server. The cloud computer starts on demand and sleeps when idle. Saved webpage files and a running service are different things; do not treat it as a personal server that stays on forever.

2. Create a dedicated Workspace

The welcome screen lets you explore an example first. To save your own work, choose the option to create a Workspace. If you already have one, open the workspace switcher near the top left and choose “New Workspace.”

Fill in the following:

  • Name: Weekend Walking Club, so you can identify it among other projects.
  • Time zone: Check that it matches your plans. Members and Agents share this time zone.
  • Where the Agent works: Select “Cloud computer” for this exercise. “My own computer” requires connecting your device. A dedicated Mac option, if shown, depends on availability and account conditions. Neither is required here.
  • Cloud computer location: Review the suggested region and choose with your location and your main collaborators in mind.

Click “Create Workspace” and confirm that the correct name appears at the top left. If creation is unconfirmed, check the workspace list before following the error instructions. Avoid creating several identical spaces while the result is uncertain. See Cloud and personal computers for runtime options.

3. Choose an Agent and a model separately

A new conversation asks which Agent you would like to start with. Choose an available Agent such as Codex or Claude Code, then check the compatible model in the menu near the input box. The Agent is the execution entry point; the model handles understanding and generation. Choosing one name does not permanently determine both.

Choose an Agent that can create and inspect files. If the interface reports insufficient usage, a required plan, an unavailable model, or a disconnected computer, address that particular message. Changing models may resolve a capability or usage mismatch, but it will not connect your computer. If no model is available, read the remaining steps and send the task once the requirements are met.

4. Send a task with clear completion criteria

Copy the instructions below. They describe the activity, permitted work, output location, and checks, so the Agent does not have to guess what “make a webpage” means.

Cards showing a route, a time, and a checklist come together in one task brief.
Put the activity details, goal, and checks into one request.
text
Create an English invitation webpage for the “Weekend Walking Club.”This is a fictional exercise. Clearly label the page “Example event.”
Activity: A relaxed weekend walk, with no speed competition and breaks whenever needed.Time: Saturday at 3 p.m. State that this is an example, not an actual event date.Meeting point: South gate of Sycamore Park. State that this is a fictional location.Route: Meet at the south gate → walk by the lake → rest on the lawn, about 90 minutes.Bring: Water, comfortable shoes, and a hat. Postpone if it rains.Joining instructions: For a real event, contact the organizer to confirm the date and location.
Make the time and meeting point prominent and readable on a phone.Add a “How to join” button that jumps to the joining instructions on this page.Do not collect registrations or add a login, map, or external images.
Save the complete page as weekend-walk/index.html in the workspace.Keep the styles inside this file; do not depend on other files or external resources.Do not just paste code into the conversation. Do not publish it publicly yet.Check that the information is complete and the button targets the right section.Tell me where you actually saved it, what you checked, and what remains unchecked.

Before sending, review the filename and activity details. If voice input is offered, you can dictate and then inspect the transcription. Times, names, and paths deserve particular attention.

5. Follow the work and answer questions that need you

Once the task starts, the conversation shows responses and work activity. The Agent may read files, write the page, and run checks. If it supplies a plan, you will also see step states. A missing final answer does not necessarily mean it is stuck; first check the current step and any errors.

If it asks about style, reply with something concrete, such as “A relaxed invitation to friends, without exaggerated language.” An initiator approval request is different: read the action and its target before deciding. You can cancel the request if you do not understand it. The available approval buttons can differ by Agent.

Messages sent while the Agent is busy enter its queue. For this first exercise, waiting for one task to finish before adding another makes it easier to see what each instruction changed. Everyday conversation and revision covers queues, stopping, and continuing in more detail.

6. Open the actual file and check your result

Click the file card in the response, or open “Files” in the sidebar, enter weekend-walk, and click index.html. HTML can be previewed by default, and you can also inspect its source. This example keeps text and styles together for direct inspection.

A webpage in a folder connects to desktop and phone views, with a magnifying glass for inspection.
Open the saved file and check its content and button at different widths.

Check individual requirements rather than only the overall appearance:

  1. The page includes the event name, “Example event” label, time, location, route, and preparation notes.
  2. Narrowing the preview keeps the text readable without horizontal overflow across the page.
  3. Clicking “How to join” reaches the joining instructions.
  4. No registration form or login requirement has appeared.

“Checked by the Agent” is not the same as opening and clicking through it yourself. Note one real issue, such as “The meeting point is cut off in a narrow view,” and use it in the next chapter.

What you seeWhat to do next
Code in the answer, but no file in FilesSend: “Please actually save the webpage as weekend-walk/index.html and confirm the save.”
Missing images or styles when opening the fileExplain that this is a single-file exercise and ask the Agent to check for external dependencies.
The file will not open, or the task failedProvide the exact error, the step where it occurred, and the file path. “It doesn't work” is not enough.
The content still looks oldConfirm you opened the right file and refresh it.

You have succeeded when you can find the file, open it, and explain what you checked. Continue with Everyday conversation and revision, then read Teamwork when you want others to review or edit it with you.