A developer harness for Muse: plan with human sign-off, build in reviewed slices, red-team the result, and ship with a record of what you learned.
Muse reads your project memory and LEDGER.md, works through decisions one question at a time with tappable choices, and prepares SPEC.md and a sliced PLAN.md. You review and approve both before coding starts.
Each slice goes to a fresh subagent. The commanding agent reviews it against the spec and reports progress before the next slice begins. A fresh red-team agent tries to break the build in its actual interface. The release checklist and ledger record what shipped and what was learned.
Give Muse the TGL repository and say “install TGL.” Confirm it can read the installed SKILL.md, then say “TGL, plan the next feature in this project.” After approving SPEC.md and PLAN.md, say “go attack mode.”
Ask Muse to connect to https://tgl-summitx.fly.dev/mcp for skill delivery and temporary planning tools. Before Meta directory approval this uses a custom integration in Muse's environment. The installed skill directs the complete development workflow using Muse's own tools and permissions. This server stores planning state and returns files; it does not execute builds. Human approval is an instruction Muse follows, not a server-side execution permission.
tgl_install: return the complete skill bundle and integrity manifest.tgl_plan_start: create a planning session.tgl_plan_log: record one question and answer.tgl_plan_goal: record the goal after at least one answer.tgl_plan_spec: validate structure and store a spec.tgl_plan_plan: validate structure and store a plan after a spec.tgl_plan_delete: delete a session at the user's request.No TGL account, payment, or API key is needed. Hosted access has no TGL fee today. Muse access is separate. Requests are limited to 120 per minute per source IP and 1,200 per minute for this instance. Shared networks may share a limit. Request bodies are limited to 512,000 bytes; short inputs to 20,000 characters; documents to 200,000 characters. Each session holds up to 200 Q&A exchanges and 1,000,000 content characters. This instance holds up to 1,000 sessions and 16,000,000 content characters.
Keep the session id private: it permits edits and deletion. Shareable document links allow anyone who has them to read those documents. They do not permit edits. Sessions expire after 24 hours without a successful write; reads do not extend them. Restart, redeploy, or capacity eviction may remove them sooner. Save your documents locally.
Run by Sendable Studios, the developer brand of Summit X Digital LLC. Contact support.