# pascalorg/editor

Source: [GitHub](https://github.com/pascalorg/editor)  
Feed7 permalink: https://feed7.dev/p/editor-1ffbppp  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

Pascal exposes a local-first 3D building editor through a CLI and MCP, giving agents structured scene tools while keeping projects on the local machine by default.

## Source Summary

Pascal is an **open-source, local-first 3D building editor** built with React Three Fiber and WebGPU. Its CLI starts the editor and an authenticated **MCP service**, while projects persist in a local SQLite database.

## Practical Implication

Builders can connect agents through pascal mcp connect and install workflows for scene work or bounded furniture-fit checks. Use separate PASCAL_HOME directories and service processes when independent agents must work concurrently.

## Agent-Ready Context

Pascal is an **open-source, local-first 3D building editor** built with React Three Fiber and WebGPU. Its CLI starts the editor and an authenticated **MCP service**, while projects persist in a local SQLite database.

Builders can connect agents through pascal mcp connect and install workflows for scene work or bounded furniture-fit checks. Use separate PASCAL_HOME directories and service processes when independent agents must work concurrently.

The npm beta is older than the repository’s **GitHub prerelease**, and optional tool fields may differ between installed and hosted versions. The project also requires one active agent client per local CLI service.

## Connected Context

Feed7 judgment across 732 accumulated Signals:

This extends MCP-backed agent work into a persistent local 3D scene editor, with bounded spatial workflows rather than browser or data retrieval. It also makes deployment topology part of the harness: concurrency requires separate homes and services, each service supports one active client, and clients must account for tool-schema drift between releases.

- [ChromeDevTools/chrome-devtools-mcp](https://feed7.dev/p/chrome-devtools-mcp-0ow49x2) — Both create an inspect-act-verify loop over a visual environment through MCP; Pascal applies that pattern to editable 3D scenes, while Chrome DevTools applies it to running web applications.
- [Expanding Managed Agents in Gemini API: background tasks, remote MCP and more](https://feed7.dev/p/expanding-managed-agents-gemini-api-1idue29) — Gemini’s remote MCP support contrasts with Pascal’s local, single-client service topology, so adopting Pascal in managed or concurrent workflows requires explicit per-agent service isolation.
- [Build-Time vs. Run-Time: Why Dev Tools Fail in Production — Averi Kitsch & Prerna Kakkar, Google](https://feed7.dev/p/build-time-vs-run-time-why-dev-tools-fail-in-production-averi-kitsch-pre-0b01i4o) — The build-time versus run-time warning qualifies Pascal’s authenticated tool access: authentication alone does not determine safe authority, so scene-changing workflows still need bounded operations and review appropriate to their execution context.

## Context Map

- Layer: tools
- Domains: image
- Topics: mcp, tool-use, skills

## Uncertainty

- The npm beta is older than the repository’s **GitHub prerelease**, and optional tool fields may differ between installed and hosted versions. The project also requires one active agent client per local CLI service.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.