** Studio 장소와 로컬 codebase 사이의 semantic 파일 시스템 브리지, 읽는 기계, 이유 및 refactor.**

Rojo Compass는 roxo-mcp]]에 대한 sibling 프로젝트이지만, 다른 철학적 자세를 가지고 있습니다. 대신 Filesystem을 Studio 세션의 수동 미러로 치료하는 대신 Filesystem을 living map으로 처리합니다. — 그 에이전트는 주석, 쿼리, 그리고 자연 언어에 대한 이유를 할 수 있습니다. 어디 roxo-mcp MCP 클라이언트와 Roblox 스튜디오 사이의 단단한 수송 루프에 초점을 맞추고, Rojo Compass는 ** 미터 층에 초점을 맞추고 ** 그 수송의 상단에 앉아 : 프로젝트 topology, 의존성 그래프, 기호 지수, 세션 전반에 걸쳐 생존하는 의도적 기록.

roxo-mcp가 신경계인 경우, Rojo Compass는 인지적인 지도입니다.

---

이름 뒤에 아이디어

Rojo (잘 사랑된 Roblox 파일 시스템 동기화)는 당신에게 양방향 다리를 제공합니다. Compass는 ** orientation**를 제공합니다. 나침반은 배를 이동하지 않습니다; 그것은 당신이 다른 모든 것에 관계되는 곳에 당신을 말합니다.

🧭 Rojo Compass — Project-Aware Roblox Sync for Autonomous Agents

A semantic filesystem bridge between your Studio place and your local codebase, built for machines that read, reason, and refactor.

Rojo Compass is a sibling project to roxo-mcp, but it takes a different philosophical stance: instead of treating the filesystem as a passive mirror of a Studio session, it treats the filesystem as a living map — one that agents can annotate, query, and reason about in natural language. Where roxo-mcp focuses on the tight transport loop between MCP clients and Roblox Studio, Rojo Compass focuses on the meaning layer that sits on top of that transport: project topology, dependency graphs, symbol indices, and intent records that survive across sessions.

If roxo-mcp is the nervous system, Rojo Compass is the cognitive map.

---

🌌 The Idea Behind the Name

Rojo (the well-loved Roblox filesystem synchronizer) gives you a two-way bridge. Compass gives you orientation. A compass doesn’t move the ship; it tells you where you are relative to everything else. Rojo Compass does exactly that for AI agents operating inside a Roblox project: it answers questions like “where does this RemoteEvent actually get consumed?”, “which ModuleScripts are orphaned?”, “what changed between the last two agent sessions?”, and “which parts of this place graph are safe to refactor without touching the UI layer?”

The repository ships three cooperating pieces:

1. A semantic indexer that walks your Rojo project tree and produces a queryable graph of scripts, instances, services, and cross-references.
2. A status & query daemon that exposes this graph over a small local protocol — designed to be MCP-adjacent but protocol-agnostic so any agent runtime can talk to it.
3. A Studio-side observer plugin that connects to the daemon on its own initiative, feeding live instance state back into the index without any manual pairing step.

Together, these three pieces let an autonomous agent understand what the project is, not just what files exist.

---

✨ What Makes This Different

Most Roblox tooling assumes a human is at the keyboard. The human remembers that ReplicatedStorage/Shared/Net.lua is the network wrapper, that ServerScriptService/Services/ holds all the service singletons, that the PlayerData module is a leaf dependency. Agents don’t have that intuition unless someone encodes it.

Rojo Compass encodes it — automatically, incrementally, and in a form both humans and machines can read.

• Instead of parsing Luau with regexes, it builds a real symbol table using a tree-sitter grammar, so re-exports, aliases, and dynamic require calls are tracked with reasonable fidelity.