From a rough plan to a checkable scenario.

Build for free with your own AI

Sign up free to connect Codex, Claude Code, or another MCP client. Ask your AI to create and edit 2D/3D spaces, check routes, and export or restore project files you keep yourself. You can also explore and edit Studio without an account. Pro adds simulation runs and comparisons (including via MCP), AI-assisted drafting, the built-in assistant, and optional cloud saving. See Account for current Pro pricing and availability.

1. Open a starting point. In Studio, choose New space. Try an office floor, office building, factory, mall, two-storey home, or a blank floor. Samples are illustrative, not measured sites.
2. Describe the layout to AI. Follow the MCP connection steps, then tell your agent what to build or change. Review the floor, parts, and connections in 2D or 3D. You can also adjust them manually in Studio.
3. Check before calculating. Use the free Route check in Studio or ask your agent to call check_space. It identifies overlaps and narrow passages, and can test reachability when you specify route targets. It does not run a simulation.
4. Keep a copy. Open Export and download a project JSON file. You can open that file in Studio later.

Model a space in 2D, 2.5D and 3D

Choose 2D plans to see all levels of a multi-storey project side by side at the same scale. Open a sheet or use the level buttons to navigate. Level layout arranges the areas on one level; Edit area opens its parts, dimensions and drawing tools. Level buttons keep you in area editing when you are already editing. All levels returns to the overview. In 3D model, choose Whole buildingor Edit area. Hologram, Blueprint and Solid are 3D visual styles, separate from which level or area you are viewing.

Agents can set {"dimension":"2d","scope":"building","planLayout":"all-levels"} with set_space_view. Set planLayout="level" to arrange the active level, or scope="floor" to edit and play a simulation in the active area. The overview shows layout sheets; playback appears inside an area.

The plan and perspective views show the same editable spatial model. A floor can have a polygon outline and holes; a part can be a box or a polygon prism, rotated and raised above the floor. This is efficient for layouts and routes, but it is not a free-form mesh or detailed CAD model.

A level is a storey. It can contain several separate floor areas. Areas that touch are not connected automatically: add a passage, stairs, elevator or escalator. Use one continuous floor with walls and doors for rooms linked by a corridor. Route checks can cross explicit connections.

A site can hold several buildings: apartment blocks, a warehouse and an office block, towers, a parking garage. Put each up under Buildings on the site with its storeys, and optionally a lift and stairs; the ground under it opens for its footprint. The ground and the bridges between buildings stay separate floor areas. Show one building alone, copy it, or drag it on the level plan with its entrances. People and robots still move only along connections, and a scenario can send them to places in one building.

With nothing selected, Areas & counts under the properties shows the floor area (the outline less its holes), the zoned and unzoned area, each zone's area, areas by tag and part counts by type. Levels & areas adds each level's floor area and the total. Overlapping zones count once in the totals. These are areas of the drawing, not a legal floor area. Zone and part names on the 2D plan move off shelving and turn to fit narrow aisles, so they never sit on each other.

Agent coordinates are in metres: x goes right, z goes toward the near edge, and y is the underside's elevation above its floor. A part's rotation is counter-clockwise degrees on the plan. Ask get_space for the current floor IDs, part IDs and revision before changing them.

Connect Codex, Claude Code or another MCP client

A connected agent uses the same open Studio workspace that you see. You supply your own agent; its provider's usage charges are separate from Laydyne. Space editing and scenario preparation through MCP are free.

1. Sign in to a free Laydyne account and leave Studio open in your browser.
2. Choose Connect AI → Create agent link. Select your client and copy the command or MCP configuration shown there. The link includes a private editing key.
3. Add the connection to your client, then reopen its session so it loads the new tools. Ask it to call get_space first.
4. Review edits in Studio. Ask for check_space before any paid calculation, and use Undo if an edit needs reversing.

The usual sequence is get_space → create_space, edit_space or edit_floors → check_space. Edits use the latest revision so an agent does not silently overwrite a newer change. get_process_catalog describes the scenario schema and samples; put_process_scenario saves a validated definition without running it.

Your working project is saved in the browser. MCP links use a Laydyne server relay that temporarily stores tool requests and results for delivery; this is not cloud project saving. Experimental WebMCP lets a compatible browser agent call the free editing tools directly in the page without that relay or a Laydyne account. Neither path promises offline use: app loading, account and plan checks, and AI provider requests can still use the network. Your AI provider’s fees and data policies apply separately.

Build large models with a program

When a layout follows rules (identical storeys, several blocks of flats, a corridor width changed in every building), ask your agent to write a program instead of making hundreds of tool calls. The program builds the site with the Laydyne kit, checks it on your machine with the same checks Studio uses, and sends the result through MCP. Checks, Undo and saving still happen in your open Studio.

1. Read the format. get_project_schema returns the saved project format as JSON Schema, one part at a time, with its rules: floors sit on the site in site metres, and everything on a floor (parts, connection ends, scenario points) uses that floor's own metres.
2. Use the kit. /sdk/laydyne-kit.mjs on this site is one JavaScript file for Node.js with no dependencies (types: /sdk/laydyne-kit.d.ts). It places parts, walls and doors, stacks a building's storeys with a lift and stairs, connects floors, assembles scenarios, and checks the result.
3. Apply only what changed. apply_changes adds, replaces or removes whole floors, buildings, connections and scenarios by id. Everything else stays as it is, including your own edits in Studio. With dryRun it first shows what would be added, replaced or lost, and fingerprints stop it from overwriting a floor you have changed by hand since.

One apply is one Undo step. Large change sets are sent in ordered chunks with a checksum. The format, the kit and applying changes are free; running simulations needs Pro.

WHY SIMULATE?

Choose what to change before spending money on it

A store manager may need to choose where to add staff. A factory engineer may need to choose which workstation to move. A robot integrator may need to narrow a fleet proposal before an on-site trial. Compare those choices against the same demand, a deadline or a service target.

1. Name the decision. Can a shorter replenishment route handle the expected work before adding a second stock assistant?
2. Record the current operation. Measure arrivals, routes and processing times. Check that the baseline resembles the site before trusting a different layout.
3. Compare achievable options. Keep demand fixed. Compare the current layout, a moved drop zone and an extra assistant. Change one factor at a time to see which one helps.
4. Read the result against a target. Check completion, waits, blocked routes and workload together. A fast average can hide jobs that never finish.
5. Connect the difference to a real cost. Include paid hours, equipment, installation, supervision and the cost of the change. Validate the promising option on site.

When does this affect sales?

Lower waits could help serve customers who previously left, but the current apparel example sends every shopper through the same journey and does not model lost sales. An estimate of additional gross profit would need measured recovered purchases and gross profit per purchase, with additional operating costs deducted. Do not turn simulated wait reduction into a sales percentage.

General workflow examples calculate operational measures, not a complete financial forecast. The separate cleaning/transport robot comparison can use supplied labour and robot cost inputs; it still needs site validation. Layout drafting also has value: measure the time needed to prepare, revise and explain a proposal with your existing workflow and with Laydyne.

Compare a robot investment with a layout change

Open the AMR line supply study to compare the current layout, a second robot and a closer pickup. Play in 3D, follow AMR 1, or switch to the same plan in 2D. Loading, loaded travel, unloading and empty return follow the recorded schedule. The live counters describe the displayed time; the table always covers the full hour. Switch options without changing the time to inspect the same moment.

Choose an option and open its project in Studio. Editing and saving a JSON file are free; running changed inputs requires Pro. The moved pickup assumes material is already at line-side staging. Include the upstream replenishment work and setup cost in an investment decision. Human and robot appearance can be selected in the process conditions without changing physical parameters.

Open an apparel store, make three changes and keep the project

Start with Apparel fitting & checkout. The public page shows an actual 3D render, the same model in 2D and recorded engine output. Select Open this example, then confirm the replacement in Studio. Export your existing project first if you need a file copy.

1. Edit in 2D. Switch to 2D. Move the feature table 1 m toward the shopfront, widen one clothing rail from 2.2 m to 2.6 m, then rotate the new-collection display from 12° to 0°. Check each change and undo it if needed. Example dimensions are assumptions.
2. Inspect the same model in 3D. The objects, floors and scenarios stay together; changing the view does not create another project. Use Route check between the arrival, browsing, fitting and checkout zones.
3. Save and restore for free. Choose Export → Project JSON. Reopen it from New space → Open project. Both the geometry and the chosen 2D/3D view are saved, along with scenarios and frozen comparisons. Saving geometry changes does not update an old result.
4. Run a fair comparison with Pro. Return to the original geometry before reproducing the published result. The project includes four scenarios and four frozen options: 2 fitting rooms / 1 checkout, 2 / 2, 4 / 1 and 4 / 2. Run or compare those inputs under the same 36 arrivals. Compare completed jobs and waiting together.

For another store workflow, try Apparel replenishment. It includes a mezzanine stockroom, explicit lift connection and one-versus-two-staff comparison. It models transfer jobs and the return journey, not inventory or sales.

Choose the calculation that matches the question

Define the workload first, then run a simulation with an active subscription. The calculation engine runs in the browser; results are computed from the model and scenario, not guessed by a language model.

Open New space → Simulation examples, or use the header’s Simulation · Pro button. The gallery has 21 examples: Service queue, Transport, Warehouse picking, Venue registration, Mall visitors, Factory flow, Home chores, Building deliveries, Café service, Inspection & rework, Apparel fitting & checkout, and Apparel replenishment. The public example library includes project downloads, recorded results and direct links to open each example. Each explains the flow, what to change and which results to watch. Spatial examples can open their layout and scenario together. Opening an example does not run it.

In the simulation panel, choose Run simulation · Pro, then Play agents on the plan to see the calculated routes in 2D or 3D. Both controls appear above the scenario inputs. Free accounts can explore layouts and edit inputs; execution requires Pro. For a custom process, ask your agent to inspect get_process_catalog and list_process_scenarios, then save a full definition with put_process_scenario. Use goto for paths through modeled floors and links; the simpler move step travels between coordinates and ignores obstacles.

See the worked questions for multi-level warehouse transport, venue entry flow, and office cleaning coverage. Each example lists the inputs and the boundary of its model.

Read and compare results

Compare variants with the same geometry, workload, time horizon and random seed unless that input is the variable you are testing. Change one assumption at a time and record its source. Process scenarios can report completed and blocked jobs, wait times, resource use and movement traces. When a layout changes, its previous process result is marked stale; rerun it before citing its numbers.

Repeating a scenario with the same seed reproduces its result. Multiple runs show spread when a scenario contains random arrivals, durations or branches. Reproducibility does not prove that a site behaves the same way. Enter real measurements and compare with observed operations before using a result to make a deployment decision.

Save and export your work

Studio keeps the working project in this browser. Use Export → Project file to download a portable JSON copy, and New space → Open file to open it later. An MCP link edits the open tab; it is not a headless project repository. Keep your JSON files if you manage data with Codex or Claude Code.

Export → 2D drawing… saves a scaled sheet of this floor area, this level or every level as SVG or PNG: a standard scale chosen to fit the paper (A4 to A1), a scale bar, outline dimensions, zone names with their areas, an area table and a title block with the project, the date and the space version. Zones too small for their name are numbered in the table. Add a north arrow at the angle you set; the model does not store true north. Export → 3D image saves the 3D view you see as a PNG, captioned with what it shows and the same space version, so a drawing and an image can be matched to one model. Your agent gets the same sheet with get_view_image in 2D (format: "svg" returns the SVG to save).

Your MCP agent can use export_project to save the whole project as JSON and import_project to restore it. Both are free, including all floor areas, saved layout comparisons and view settings. Restoring a project does not run a simulation. Undo returns to the project you had before the import. Keep Studio open while your agent transfers the file, and ask it to verify the completed download before replacing your backup.

If Cloud projects is enabled on your plan, saving there is a separate action. Opening a cloud project loads it into the browser workspace; later changes remain local until you choose to save them to cloud again. The original drawing or photo is not included in the saved project; keep the source file separately.

What the result can and cannot tell you

Results come from a simplified, deterministic model: robots are circles moving at constant speed, and the same input always gives the same result. It does not model collisions or avoidance between robots or people (only capacities and queues), crowd physics, elevator dispatch, turning, charging and batteries, or cleaning quality. Dimensions read from photos and drawings are assumptions to check against measurements. It is for exploring options, not a calibrated prediction of a real site.

• Process scenarios count capacities and FIFO waits, but do not model collision avoidance, passing, crowd pressure or density-dependent walking speed.
• Elevator travel uses speed and capacity; dispatch and stop selection are not modeled. Waits may therefore be too low.
• Door opening time, acceleration, turning, charging, breakdowns, evacuation and safety-code compliance are outside the model.
• A route check verifies the simplified geometry and declared clearances. It cannot verify that your drawing, object sizes or operational assumptions match a real site.

Use Laydyne to narrow options and expose assumptions. Confirm critical clearances, throughput and costs against measurements and specialist tools where required.

Troubleshooting

My MCP agent cannot reach Studio.

Keep the linked Studio tab open, reopen your AI client after adding its MCP configuration, and create a new link if the old one ended. Do not publish the link key.

An edit says the revision is stale or times out.

Ask the agent to call get_space before retrying. A timed-out edit might already have applied, so inspect the current model first.

A route cannot reach another floor.

Check that the two floor areas have an explicit connection, the agent type may use that connection, and no anchor or passage is blocked. check_space can return a route-failure reason.

A simulation says subscription required.

Editing, route checks and scenario definitions remain available. The execution tools require active simulation access; check the plan shown in your account.