スタジオの場所とローカルのコードベース間のセマンティックなファイルシステムブリッジ、読み取り、理由、およびリファクタのために構築されています。

Rojo Compass は roxo-mcp] に兄弟プロジェクトですが、異なる哲学的スタンスを取ります。代わりに、Studio セッションのパッシブミラーとしてファイルシステムを処理する代わりに、それは** リビングマップ** としてファイルシステムを扱います。エージェントが自然言語で注釈付け、クエリ、そして理由をすることができます。 [roxo-mcp は、MCP クライアントと Roblox Studio の間の緊密な輸送ループに焦点を当てるところ、Rojo Compass は、プロジェクトトポロジー、依存性グラフ、記号インデックス、およびセッション全体にわたって生き残っている意図的なレコードの上に座っている**のレイヤーに焦点を当てています。

[roxo-mcpが神経系の場合、Rojo Compassは認知マップです。

お問い合わせ

の名前の後ろのアイデア

Rojo(よく愛されているロブックスファイルシステムシンクロナイザー)は、双方向のブリッジを提供します。 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.