Public dashboard
Vercel production is published
Your public dashboard is live. Linux packages and the offline desktop window have passed CI. The next milestone is a verified, private path from ChatGPT to your local Forgejo server.
See what is still missing →Browse public projects ↓Vercel production is published
AppImage + Debian packages built
Process daemon: x64 + ARM64
Import a current Ubuntu report. The saved Forgejo HTTP 403 is historical; it does not establish today's access.
Check local HTTP reachability →Verify an authorised read, MCP initialization and tool discovery on the local server. An HTTP response alone does not prove these work.
Verify an authenticated private bridge and one read-only tool call from ChatGPT. Local JSON imports cannot complete this milestone.
Test installation, upgrade and rollback on Ubuntu, plus a physical-GPU desktop session. The latest audit has 15 moderate packaging-chain findings; high and critical findings are cleared.
Read scope and remaining limits ↗Some public upstream jobs are queued on Blacksmith runner labels. The passing native process-daemon checks do not cover those Bun and Nix suites.
Inspect queued workflows ↗The CPU/debugger harness is tested; the instruction step is still a placeholder. Guest execution, graphics and a game boot remain unverified.
Ubuntu · port 3000
Ubuntu · port 8787
Cloud bridge
Loading actual public repositories from GitHub. Private repos and Forgejo repositories are not included.
This is a read-only public repository view. It doesn't connect to local Forgejo, run CI, use tokens, or claim your private code is available.
Run the exporter on Ubuntu, then import its JSON here. It records HTTP status observations without tokens, repository contents or response bodies. Your file stays in this browser; importing it does not establish a live or authenticated connection.
No report imported.
python3 tools/dragonhub_readonly_export.py \ --output "$HOME/Downloads/dragonhub-status.json"
Run from your RepoForge checkout. View the read-only checker ↗. HTTP 403 means access was refused.
Inspect Forgejo API and MCP protocol, not just the listening ports.
Verify the installed version and a scoped read-only credential locally.
Use an approved private tunnel or authenticated HTTPS MCP service.
Discover tools and read a real repository, then cross-check the Forgejo UI.