Describe it. Pisces builds
the whole game.

A coding agent proven on 3,500,000+ live Roblox visits — it greps your codebase, researches live docs, and ships reversible patches into your open Studio. Five more studios handle UI, models, motion, and sound.

Free: 1 credit a day while your plugin's connected · Marketplace plugin · 60-second install

pisces · turn replay studio connected

The suite

One subscription. Six studios.

Everything below ships real assets into your open Studio through the same plugin bridge — no exports, no imports, no copy-paste.

Code /web

The agent. Greps your place, researches live Roblox docs, ships line-precise reversible patches, then runs a playtest to verify them.

Open studio →
Design /design

Describe an interface; get a finished Roblox UI — device-aware layout, styled buttons, wired into your PlayerGui.

Open studio →
Modeler /model

Text to parts, meshes, or an entire composed map — baked, textured, and inserted where you asked for it.

Open studio →
Animator /animator

Describe a motion; get a finished animation published to your rig — combat moves, emotes, multi-character cutscenes.

Open studio →
Effects /effects New

Particle VFX tuned against a hand-graded reference library — abilities, auras, slashes — choreographed and previewed live, pushed straight to Studio.

Open studio →
Audio /audio

The sounds your game needs — generated, auditioned in the browser, uploaded to your universe with ready-to-use sound IDs.

Open studio →

Case Study / N° 001

3,500,000+

Total recorded visits on 99 Nights in the Ocean, a live Roblox title whose debugging and feature-build workflow has been supported by Pisces. Not a pitch — a receipt.

What the number means

99 Nights in the Ocean.

The same agent you'd pay $20/month to use has already been trusted on a production title with an order of magnitude more players than most games ever see.

01 — Scale

More than 3.5M live players.

Pisces has shipped debug fixes and features inside a game played by millions. If it can keep a production title shippable under load, it can keep your solo project shippable under ambition.

02 — Complexity

Real multi-script systems.

Inventory, combat, matchmaking, data stores, anti-exploit —  not toy demos. Pisces traces the full client↔server↔module dependency chain and patches all of them in one coherent pass.

03 — Proof

You can open it.

We're not hiding behind a logo wall. The game is live on Roblox. Click through, see the scale, watch a playtest, then come back. Open on Roblox ↗

How it thinks / Every turn is a receipt

Read. Research. Then write.

Other AI dev tools start typing the moment you press send. Pisces opens your project like an engineer would — reads, confirms, and only then edits. Every turn leaves a receipt.

01 / READ

Greps before it guesses.

Pisces indexes every script, remote, UI node and folder in your place on session start. When you ask a question, it greps the real tree, not a hallucinated one.

>> tool_use: grep
pattern: "InventoryService"
paths:  "ServerScriptService/**"

<< tool_result
ServerScriptService/Main.lua:42
ServerScriptService/Inventory.lua:17
ReplicatedStorage/Shared.lua:88

✓ 3 real matches · 0 inventions
02 / RESEARCH

Checks live docs.

When Roblox APIs shift, Pisces queries current docs and DevForum before committing. No more 2022-era FindFirstChild advice on a 2026 API.

>> tool_use: web_search
query: "CollectionService 2026"

<< tool_result
 GetInstanceAddedSignal → RBXScriptConnection
 GetTagged returns {Instance}
 No deprecation warnings in 2026 API

confirmed · ready to write
03 / WRITE

Surgical. Reversible.

Line-precise patches that respect your whitespace and your comments. Every edit hits the undo stack so a single click rolls it back — no rbxl corruption, ever.

>> tool_use: fix_script
target: "Inventory.lua:42"

- player.Character:FindFirstChild("Inv")
+ player:WaitForChild("PlayerInventory", 5)

✓ Shipped · undo ready · 0.2s

The interface · browser + Studio

What you see in the browser.

The chat lives at piscesofficial.com. The plugin's just the bridge — it listens for tool calls, executes them in your open Studio, reports back. You never type into Studio. You never leave this tab.

piscesofficial.com/web
● connected · baseplate
Pisces / Pro
74 credits · session live
▼ Action plan
Indexed 168 scripts · 22 remotes from open place
Running Bug Analyst + Codebase Scout
Apply guarded patch · queue Studio for verify

[bridge] plugin online · 168 scripts · poll 14 ms

Find why inventory items vanish after equip.

thinking: tracing server validation path…

◆ Analyzing with 2 specialists
[◔] Codebase Scout  —  InventoryService
[◑] Bug Analyst  —  DataStore sync
ask Pisces to build something…

Browser chat, Studio edits

You type at piscesofficial.com. The agent runs server-side, calls tools through the plugin bridge, and the diffs land in your open Studio in real time. No IDE plugin chat panel, no second window to keep alive.

Specialist subagents

Complex debugging dispatches role-based investigators (Codebase Scout, Bug Analyst) with a live status panel and a merged report. Not one generic pass.

Runtime error capture

Output-window errors are grabbed from the plugin during playtest, surfaced in the browser as one-click fix requests with the full stack trace attached.

Guard-railed by default

Server-side syntax check on every patch: block balance, missing end, wrong method syntax, scope errors — caught before they reach the bridge.

Activity bar · one-click undo

Every tool call lands as a row in the activity drawer with a built-in ↶ Undo button. The plugin rolls the patch back through ChangeHistoryService — no AI call, no credits spent. Ctrl+Z in Studio works in lock-step.

The spec sheet

Pisces vs. Claude Code + MCP.

Claude is a genius. It's just a genius without a steering wheel. Pisces is a native Roblox vehicle, purpose-built for this one game engine.

Pisces Pro
from $20 / month · up to 400 credits
Claude Code + MCP
$20 / month · community Roblox MCP
Beyond code
Five more studios in the same subscription: UI design, 3D models & whole maps, rig animation, game audio — effects on the way. All ship through the same plugin bridge.
Code only. No UI generator, no mesh pipeline, no animation rig, no audio — you're wiring a separate tool for each.
Setup
Install one plugin from the Roblox marketplace. Open piscesofficial.com, paste the key, accept two Studio prompts. Done — about 60 seconds.
Install Claude Code CLI, set up an MCP server, wire a Roblox bridge, manage HTTP allowlists per project. Hours per machine.
Where you chat
Browser tab. The plugin is silent — no chat panel inside Studio, no second window competing for focus.
A terminal next to Studio. Or a third-party plugin's chat box. Context lives in two places.
Codebase awareness
Every script, RemoteEvent, Tool, Folder, and instance from the open place is indexed and re-synced after every edit.
Sees what the MCP exposes — usually a flat dump of script source. Misses live instance state, RemoteEvents, attributes.
How edits land
Content-anchor edit_script with a 9-fallback replacer cascade. Matches across reformat, rename, and concurrent edits without breaking.
Line-number rewrites or whole-file replacements. One reformat downstream and the patch lands in the wrong spot.
Patch safety
Pre-flight: syntax check, API-typo gate, server-script wiring guard, dup-handler scan. Bad patches die before the bridge.
Raw edits. Broken Lua ships. Your only safety net is the file you committed before the agent started.
Undo
Activity drawer ↶ Undo on every tool call (free, no credits) plus native Ctrl+Z in Studio. Both go through ChangeHistoryService and stay in lock-step.
Roll your own. git checkout, manual revert, or eat the change.
Playtest verify
Agent triggers a live Studio playtest, captures runtime errors + console output, fixes the bug, re-runs. Up to three iterations per turn.
Copy the error from the Output window yourself. Paste it back. Repeat.
Diff visibility
Every patch renders in the browser as a red-removed / green-added card with surrounding context lines. You see what landed before it lands.
Buried in terminal output or a plugin scroll. Often just the new file body, no diff at all.
Subagents
Role-specialist investigators (Codebase Scout, Bug Analyst, etc.) dispatch in parallel with a live worker panel.
One generic loop. No role specialisation, no parallel dispatch.
Skill packs
Roblox-specific skill packs (combat, anime moves, pathfinding, lighting) load on demand from production code.
Generic LLM. Whatever the model remembers, it remembers — no Roblox library.
Doc research
Live web_search against current Roblox API + DevForum in-loop. Never quotes a deprecated method.
Trains-on-snapshot, often months stale. Suggests removed APIs.
Pricing
Free: 1 credit / day just for staying connected. Plans from $20 / mo (70–400 credits, 25–28.6¢ each). Packs from $5 — metered by tokens, never expire.
$20 / month for Claude Pro plus your own time setting up + maintaining the MCP stack.

One plan, one currency

Pricing, priced honestly.

A credit is a unit of AI usage, metered by tokens — a small edit costs a fraction of one, a typical build runs under one. Credits never expire.

Free
$0
1credit / day
Every account, no card. Accrues to a 3-credit cap while your Studio plugin is connected.
Credits
37¢+/ credit
shelf life
Metered by tokens — you pay for exactly what you use, not per message.
+ One-time packs
Skip the subscription. Grab a pack. Never expires.  10 · $5  /  45 · $20  /  120 · $50  /  270 · $100
Full pricing →
Start building Install plugin ⤓

Dive.

A free credit a day. Sixty seconds to install. Six studios when you surface.

Start building Install the plugin ⤓

When Studio prompts for HTTP requests + script edits — accept both. That's how Pisces reaches your code.