~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/hud

A remote MCP server that shows atproto records as interactive UI inside MCP Apps hosts

0
0

No way to work on an app's views without a deployed HUD and accounts

Open
Open chadtmiller.com opened this issue 0 comments

What happened

There's no way to work on an app's views without a deployed HUD and real accounts. Changing one of Grain's views (next/views/*.json) today means restarting a HUD with HUD_APPS pointed at them and signing in with a real account against real PDSes, or deploying to next.grain.social. just local runs a PDS of HUD's own with alice, bob and carol, but for HUD's workspace, not for an operator's app, and it doesn't reload a view.

What's missing is hud dev <dir>: an app served from its directory as hud serve would serve HUD_APPS, its views and app file checked (hud check) and hot-reloaded as they change, with problems shown in the page, not a refused start; beside it a local PDS and PLC with test accounts seeded with the app's records (a fixture file of records per account), and the app's web shell (@hud/shell) pointed at it. The native kits could reach it the same way just local --ios does.