Pascal Editor

Pascal Editor is an open-source 3D architectural editor for builders who want a local-first design canvas that AI agents can operate. The official site describes Pascal as a way to create and share 3D architectural projects, turn a property into a living digital twin, and manage a building from one 3D canvas. The GitHub repository adds the developer angle: the editor is built with React Three Fiber and WebGPU, can run in the browser or from a CLI, and exposes MCP workflows so agents can help drive the workspace. The core workflow is simple: create, edit, and present. Users can scan or sketch a space, move walls, swap furniture, test layouts, and walk through designs in first person. Pascal also ships a capture/scanning surface, material and rendering features, and an asset library with ready-made 3D objects. That makes it more approachable than heavyweight CAD software for early planning, digital twins, game spaces, production sets, and interactive property presentations. For developers, Pascal is especially interesting because it is not only a hosted editor. The project publishes viewer, editor, scene-engine, and CLI surfaces on npm. The README says the CLI can start a persistent local Pascal installation, keep project data under a local directory, and run an authenticated MCP service in the background. That means a coding agent can be connected to a 3D scene workflow instead of treating the editor as a closed visual app. Pascal is best for teams experimenting with AI-assisted spatial design, local digital-twin workflows, or agent-controlled architectural tools. Architects and contractors can prototype layouts. Game and content teams can block out spaces. Developers can embed the viewer or editor in their own products. AI-agent builders can use the MCP and CLI pieces to test how assistants reason about geometry, floor plans, and project state. The main caveat is maturity. This is an open-source product moving quickly, and the website references advanced AI generation ideas that users should verify in the current build before depending on them in production. Treat Pascal as a promising local-first architectural editor and developer platform, not as a finished enterprise BIM suite. If your work needs browser-based 3D editing plus agent hooks, it is a strong candidate to test. For OpenTools readers, the key reason to track Pascal is the bridge between visual design software and agent automation. Many architecture and CAD products expose a polished interface but little automation surface for local agents. Pascal points in the opposite direction: browser editing for people, packages for developers, and a local command-line path for assistants. That combination gives builders a concrete testbed for spatial workflows where an agent can inspect project state, suggest changes, and help maintain documentation around a model. Teams should start with a small room or floor-plan experiment, verify the CLI and MCP behavior on their machine, and then decide whether Pascal fits a larger property, game-space, or digital-twin workflow.