A Dedicated Mac gives a coding agent a separate physical computer to work on. Setting it up successfully means more than reaching the desktop: you need the right account, the correct repository, a working toolchain, and a way to verify what the agent changed.
This guide is a delivery and acceptance checklist for Agent.Space's Dedicated Mac, based on the published product configuration. It is not a record of an end-to-end rental test. Complete the checks on the machine you actually receive.
Check what was delivered
The current offer describes an M4 Mac mini with Codex, Claude Code, the Agent.Space Mac app, and Remote Screen preinstalled. OpenCode and other tools may need separate installation. Confirm your order's specifications and delivery details against the live offer.
Before importing private work, confirm that you can access the assigned machine, identify its hostname, and use the intended administrator account. Follow the delivery instructions to change the initial password yourself. Never paste the password into an agent conversation or a support screenshot.
Physical tenancy and access control are different questions. A dedicated machine is not a promise that the operator has no maintenance access. Review the service terms and your organization's policy before putting confidential repositories or production credentials on it.
Decide which account will run the agent
A preinstalled Claude Code or Codex executable does not include an official subscription. For a local agent, sign in using your own eligible provider account. Provider terms and supported-region requirements still apply.
A supported cloud-agent route through Agent.Space has its own usage rules. Record which route you choose and where its bill appears. Machine rental, native-provider usage, and Agent.Space usage must not be treated as one unlimited allowance. The agent-versus-model explanation helps separate these layers.
Bring over one project, not your entire laptop
Start with a repository you are authorized to copy. Prefer a small test project or a clean clone without production secrets. Record its revision before asking an agent to edit it.
Check the required language runtime, dependency installation procedure, and existing test command. Preinstalled agents do not guarantee that every project's dependencies are present. If a repository requires a private package registry, arrange its approved access separately rather than asking the agent to discover credentials on your behalf.
Run a task with an observable finish line
A useful first request is:
Explain the project structure. Run the existing non-destructive check documented by this repository. Do not install new services, deploy, or edit files. Report the command, result, and any missing prerequisite.
Then try one small edit on an isolated branch or repository copy. Inspect the diff and rerun the relevant check. A confident answer in chat is not evidence that the check passed.
The first-project guide gives a task-and-review structure you can reuse. Keep the same structure when moving between Codex and Claude Code rather than changing both the environment and the task at once.
Test remote access and continuity separately
The offer lists access as an administrator account, Screen Sharing, and SSH. From another device, use the built-in Screen Sharing or SSH. From a supported Mac, you can also use Remote Screen for desktop or single-app access; its first connection must be confirmed on the Dedicated Mac. Remote Screen is Mac-only for now and its iPhone and iPad versions are marked coming soon, so do not make mobile desktop control a required part of your purchase decision.
Once the Dedicated Mac is connected to your Workspace, you can also open it with the Agent.Space Mac app's built-in remote control. The delivery steps connect it: open the Mac app in the Dedicated Mac's menu bar, select Connect, sign in, and choose the Workspace. The Remote Screen guide explains the permissions this route needs and who else can control the Mac.
To test continuity, disconnect the viewing device during a harmless task and later check the saved output. Do not interrupt the execution machine itself and assume the same result. Hardware availability also does not guarantee that an agent can continue through every permission prompt or provider limit.
Plan the exit before making the machine important
Keep important work in your approved backup and version-control systems. Know how to export files, remove credentials, and end remote-device trust before the rental ends. Check the live retention and renewal terms; do not treat the machine as a permanent backup.
If this checklist matches your needs, review the current Dedicated Mac offer. If you only need a portable cloud project, compare it with the workspace guide before renting hardware.