Macshop Guide: From Your First Task to Team and Multi-Agent Work

Learn how to use Macshop: start a Claude Code or Codex task, check files and previews, work with teammates, and choose your computer and model access.

Macshop is a workspace where people and AI Agents work together. Use Claude Code, Codex, and other Agents to write code, build webpages, or organize research, then inspect files, check results, and make changes with your teammates.

The work can run in the cloud, on your own computer, or on a Dedicated Mac. This guide starts with your first task and shows what each feature is for and where to begin.

Looking for Google's similarly named product? See Google Agentspace vs. Macshop to check which one you need.

New here? Start with one small task

  1. Create a Workspace. Sign in to Macshop and create a Workspace for your project and conversations. For a first try, choose a cloud computer; you do not need to install local development software first.
  2. Choose an Agent and a model. In a new conversation, select an available Agent such as Claude Code or Codex, then check the compatible model and available allowance.
  3. Describe the outcome. Provide the goal, materials, and acceptance criteria. For example: “Build an event information page with the time, location, and signup instructions. Make it work on phones and save the files in the project.”
  4. Open the result, then request changes. Open the output from a file card in the reply or from Files in the sidebar. Check the content, preview, and buttons before describing what needs to change.

Success means you can find and inspect the result, not just that the Agent says it is done. For a step-by-step exercise, follow Your first webpage.

Find the feature for your task

What you want to doWhat to useWhere to start
Write code, build a webpage, or work through researchConversations and filesStart a conversation, select an Agent, and supply the task and materials. Check the output in Files.
Follow several tasks and see where you are neededDynamic viewOpen Dynamic view, keep related conversations together, and find tasks that need your input.
Work with teammates and different AgentsMembers and a shared WorkspaceInvite members and agree on responsibilities. Use separate conversations for tasks around the project files.
Connect external tools or use an existing working methodPluginsOpen Plugins, then Discover plugins. Choose the capability you need and connect any required external service.
Keep project progress or useful data in viewBento widgetsIn a supported cloud Workspace, create a widget from Dynamic view. Tell the Agent its data source and what to display.
Show someone the resultFiles and downloadsCheck the saved file in its preview first, then download the files you want to hand over.

You do not need every feature at once. Complete a task in a conversation first; invite members when you need collaboration and connect plugins when you need external data.

How do multiple Agents work together?

You might have Claude Code build a page and Codex inspect the changes. Give the second Agent specific files, a goal, and review criteria instead of just saying “carry on.” Project files can support the handoff, but a different conversation does not automatically know all the background.

When several people are editing, agree on responsibilities first. Dynamic view helps you follow progress, and member permissions control who can act; neither replaces clear assignments or checking the result. See Work together, and for what a team needs before working this way, What is multiplayer, multi-agent collaboration?

If you already work in local Claude Code, you can also get a second opinion through a plugin. See how to have Codex review Claude Code's work.

When should you use plugins and widgets?

When an Agent needs to read from an external service, check for an appropriate plugin and confirm that its connection works. To keep track of project progress, ask Bento to turn a real file or connected data source into a widget.

For example: “Read the project's task table and create a widget showing completed tasks and remaining work. Include the update time.” Check the data after the widget appears; placing it on the map does not schedule daily refreshes. See Plugins and Bento.

Macshop Workspace with Codex selected in the Agent harness chooser

Cloud, your own computer, or a Dedicated Mac?

Where work runsWhen it fitsWhere to start
Cloud computerYou want to start in a browser without maintaining a local environment first.Select a cloud computer when creating a Workspace.
Your own computerYou want to use your device or connect Claude Code or Codex already installed on it.Follow the App and website guidance for the appropriate mode. Connecting an existing Agent and deploying a Workspace are different paths.
Dedicated MacYou need an independent Mac with ongoing availability, rather than relying on your everyday computer.Check Dedicated Mac specifications, rental conditions, and connection instructions.

Your own computer needs to remain available; a cloud environment does not promise that every process runs forever either. If you need a separate machine, consider a Dedicated Mac. Renting hardware does not automatically include every model or eligibility for an official account.

Use Remote Screen when you need to operate another Mac's desktop yourself. It provides screen access and control, not model access. Explore Remote Screen.

For the actual connection steps and the difference between viewing and controlling a conversation, see cloud and your own computer.

How do models, plans, and the API fit in?

Working inside Macshop: Check available combinations in the model selector. Compare models and channels in the marketplace, and see plans and usage-based costs on the pricing page. Check computer costs, model costs, and existing account costs separately; one allowance does not make every feature free.

Keeping your own Claude Code, Codex, or OpenCode setup: Use the Model API to connect to available Macshop models. Get an API key, configure a compatible model and endpoint using the client instructions, then verify a small request. Connecting an API does not automatically upload your project or migrate conversation history.

Already have a provider API key? Connecting it inside a Workspace is a different direction from the Model API above. The models and usage manual explains both paths, who pays, and where to check usage.

If your goal is a personal portfolio website and you would rather commission the result, start with a portfolio website cost breakdown and compare templates with custom work. Check the services marketplace for current availability and the specific delivery scope before ordering.

Start with what you need today

Start using Macshop. For detailed instructions, find the relevant chapter in the product manual.