Wallfacer

A computer prepared for the job.

Your employee needs a place to do the work. Give it your code, the right software, and its own accounts, with access you control.

See how it’s prepared
Your employee’s computer
  • GitHub
  • Slack
  • Email
  • Your repositories
  • App servers
  • Passwords & secrets
Your project workspace
  • yourcompany/your-repo-1
  • yourcompany/your-repo-2
  • Software and services for your project

Prepare the computer once. Reuse the setup.

Set up the project’s computer with the tools it needs, then save that setup. Later tasks can restore it instead of repeating the heavy preparation.

  1. Prepare the project

    Choose the software, check out the repositories, and configure the services the job needs.

  2. Save the starting point

    Capture the prepared setup as a snapshot that can be restored for later work.

  3. Start the next task

    Restore the saved setup, start the configured services, and bring the app to readiness.

Restoring a snapshot is one part of startup. Services still need to start and become ready; a process left running in an earlier session may not survive.
See example environment configuration

For the technical setup, a manifest describes the operating system, repositories, installation commands, and services. These Linux and macOS examples show how the pieces fit together.

agent-env.yml

version: 1
platform:
  os: darwin/arm64

sources:
  - repo: acme-corp/mobile-app
    workspace: /Users/admin/workspace/mobile-app

setup:
  - name: Install dependencies
    run: npm install

services:
  - name: api
    run: npm run serve
    ports:
      - port: 8080
        name: http
    healthcheck:
      url: http://localhost:8080/health
      interval: 2s
      timeout: 30s

simulators:
  - platform: ios

agent:
  instructions:
    - .claude/CLAUDE.md

Running in Wallfacer VM

API Server
healthyapi--vm-abc123.wf.dev
mobile-app
cloned
iOS Simulator
runningiPhone 16 Pro
MobileApp
installedDebug build

Give it the tools to check its work.

A coding employee needs to run the project, see the result, and investigate what went wrong. Its computer can hold the same tools your team uses.

Web apps and services

Prepare Linux with your app, backend, database, and browser tools. The employee can start services, run tests, and click through the changed flow.

Native and iOS apps

Prepare macOS with Xcode and the iOS Simulator. Give the employee the tools to build your app and inspect it on a simulated device.

Your project, together

Keep related repositories, project dependencies, and configured MCP tools on the computer. Choose what the job needs during setup.

Before requesting review

  1. Run the checks

    Build the project and run the tests in your handbook.

  2. Look at the result

    Open the changed flow in a browser or Simulator.

  3. Bring back the evidence

    Attach findings and screenshots. Explain anything that could not be verified.

An example procedure. Your handbook sets the checks; the computer supplies the tools to carry them out.
How the handbook guides work

Give access to the employee doing the work.

Choose which repositories and services the employee can use. Its working identity supplies the access for the session.

Explore controls and work records

Credentials belong to the session.

Per-identity credentials are supplied for the work and scrubbed before a reusable snapshot is captured.

Reasoning and tools run separately.

The agent uses tools on the prepared computer through a controlled connection. Your code and credentials live on that computer, separate from the reasoning process.

Need the computer on your own infrastructure?

Talk with us about enterprise deployment on your hardware or cloud, including private networking and dedicated macOS hosts. We’ll work through where the code runs and what your team needs to manage.

Let’s prepare your employee’s workspace.

Tell us what the job needs to run and which tools your team uses. We’ll work through the computer, access, and setup together.

Talk about your setup