What This Is
The public marketing and discovery layer.
People should land here to browse interesting things, not to manage a workspace.
withfudge.com / public surface
Reference view only. The real public landing should be a published HTML artifact route.
This asset page is no longer the target implementation for the public host. The public landing should move to a workspace artifact such as
/_Home, then be reached through host rewrites. This section remains as a temporary reference while that handoff happens.Working Today
Curated explore cards and public product framing.
This page is using a small editorial manifest because there is no backend-wide public feed yet.
Later
Real artifact pages, live feeds, creator profiles.
Those need public metadata/index contracts we do not have yet.
Artifact Page
Public unit of understanding.
Each artifact should explain itself quickly and point back into remix and studio flows.
Explore
Public unit of discovery.
Curated now, live later. The structure is ready even before global indexing exists.
Custom Domains
Public distribution layer.
Custom domains should map to published routes, not to whole workspaces.
Curated Explore
Loading curated public manifest...
Selected Artifact
Waiting on curated data...
Pick an artifact from the Explore cards to inspect the current public/product framing.
The public shell is manifest-backed for now, while live runtime and real public indexing remain separate concerns.
Public Routing
These links show how the public shell hands off to studio and runtime today.
Runtime path unavailable.
Current Truth
This view is intentionally honest about what exists now.
app.withfudge.com / studio surface
Launch workspaces, publish routes, and connect agents.
This page is the cross-workspace bootstrap shell. Once you select a workspace, the next studio surfaces can live as artifacts inside that workspace, starting with
/_StudioHome.What This Is
The cross-workspace launcher.
Use this root app to create or choose a workspace, then jump into workspace-level artifact surfaces.
Working Today
Real browser-backed admin tools.
The forms below already talk to the live backend routes for create, claim, publish, and MCP OAuth setup.
Later
Artifact-driven studio pages inside each workspace.
The first one is
/_StudioHome. Publish, connect, and editor views can follow that same pattern.If You Are Testing Today
This is the simplest way to read the current screen.
Current Workspace Map
This shows how one selected workspace connects across studio, public runtime, and MCP.
No workspace selected yet.
Choose a workspace from the list below, or create or claim one.
Bootstrap App
Waiting on workspace selection.
Workspace Studio Artifact
Waiting on workspace selection.
Runtime JSON
Waiting on workspace selection.
MCP
Waiting on workspace selection.
Public Route
No published public route loaded yet.
Studio Data
This section now uses the real browser-facing routes instead of static copy only.
Idle
No studio data request sent yet.
Current Human
Waiting on
GET /me.Workspace List
Waiting on
GET /workspaces.Create New Workspace
Pick an ID, choose visibility, then submit the real
PUT /workspaces/:id request.Idle
No create request sent yet.
Claim Existing Legacy Workspace
Use this if the workspace already exists and you still have its legacy admin token.
Idle
No claim request sent yet.
Connect Agent with Browser OAuth
This stays the default human flow. It registers a public client, runs PKCE in the browser, and exposes discovery URLs first.
Idle
No OAuth flow started yet.
MCP OAuth Ready
This studio view stores the active OAuth browser grant in session storage and leads with the MCP/discovery URLs.
MCP URL
Protected Resource Metadata
Authorization Server Metadata
OAuth Client / Grant Summary
Advanced / Debug
Access Token
Refresh Token
Manual Bearer Fallback
Published Routes
This wraps the existing browser cookie-backed
/_published-routes endpoints so public routes can be managed from the studio shell.Idle
No published route request sent yet.
Waiting on
GET /workspaces/:id/_published-routes.mcp.withfudge.com / protocol surface
One host for MCP and OAuth. Human Access only where the backend truly needs it.
This surface exists so generic MCP clients can talk JSON to the protocol endpoints without being bounced into an Access HTML login page. The only route that should stay Access-backed here is the browser authorize step.
What This Is
The machine-facing host.
Humans may pass through it during OAuth, but its main job is serving clean protocol responses to clients.
Working Today
The backend already has the MCP and OAuth routes.
This page is mostly making ownership clearer by gathering the important URLs in one place.
Needs Infra
Proper host split and Access path scoping.
Without that, generic clients can still get HTML login pages where they expected JSON.
Protocol URLs
Use any workspace ID to inspect the MCP and OAuth discovery URLs this host should own.
MCP URL
Protected Resource Metadata
Authorization Server Metadata
Authorize Endpoint
Waiting on workspace selection.
Current Constraint
This host is primarily about protocol correctness and clear ownership, not about adding new backend behavior.