DRAGONHUB PROGRESS · UPDATED 2 NOVEMBER 2026

Your code, your server.
One honest status page.

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 ↓
CHATGPT ChatGPT → local ForgejoAuthenticated tool read: unverified
↓   Authenticated MCP connection
SECURE BRIDGE Authenticated bridgeFresh readiness evidence needed
↓   Outbound connection only
UBUNTU Forgejo + DragonHub MCPLocal reachability and authenticated tools need separate checks
VERIFIED PROGRESS

Working now

Evidence checked 2 November · Melbourne
LIVE

Public dashboard

Vercel production is published

The dashboard and this page returned HTTP 200. Public GitHub browsing works without a token.
Open RepoForge →
CI VERIFIED

Linux desktop build

AppImage + Debian packages built

Dashboard tests, 17 Python checks and an offline, sandboxed Electron source-window capture passed. Physical GPU and installed-package acceptance are still open.
View build evidence ↗
NATIVE CHECKS PASS

Windows build repair

Process daemon: x64 + ARM64

Windows x64/ARM64, Linux, macOS and Miri checks passed on the merged repair. Other upstream workflows request Blacksmith runner labels and remain queued.
View native CI ↗
NEXT MILESTONES

What is still missing?

WORK REMAINS
  1. Fresh local service evidence

    Import a current Ubuntu report. The saved Forgejo HTTP 403 is historical; it does not establish today's access.

    Check local HTTP reachability →
  2. Authenticated Forgejo and MCP access

    Verify an authorised read, MCP initialization and tool discovery on the local server. An HTTP response alone does not prove these work.

  3. A real ChatGPT-to-Forgejo read

    Verify an authenticated private bridge and one read-only tool call from ChatGPT. Local JSON imports cannot complete this milestone.

  4. Desktop acceptance and dependency follow-up

    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 ↗
  5. Runner capacity for upstream checks

    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 ↗
  6. Seed ARM64 guest execution

    The CPU/debugger harness is tested; the instruction step is still a placeholder. Guest execution, graphics and a game boot remain unverified.

Read the full activity and missing-work report ↗
CONNECTION HEALTH

What is actually working?

Awaiting local report
UNVERIFIED

Forgejo API

Ubuntu · port 3000

Waiting for your local read-only check.
UNVERIFIED

MCP transport

Ubuntu · port 8787

Waiting for your local read-only check.
TO VERIFY

ChatGPT → local Forgejo

Cloud bridge

Only a real tool call from ChatGPT can verify this.
LIVE · PUBLIC GITHUB ONLY

Repository activity

Source: GitHub public API · Never Forgejo

Loading actual public repositories from GitHub. Private repos and Forgejo repositories are not included.

Checking public GitHub…

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.

SAVED FORGEJO CHECK · HTTP 403

Import a fresh report to check access

A previously saved Ubuntu check returned 403 for /api/v1/version. That records a reachable port refusing access at the time of the check. Import a new local report to see a newer result.

ZERO-CREDENTIAL DIAGNOSTIC

Import a local status report

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.

UBUNTU TERMINAL · READ ONLY
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.

SAFE PATH TO CHATGPT

Four checks before enabling tools

  1. Verify local services

    Inspect Forgejo API and MCP protocol, not just the listening ports.

  2. Check authorised access

    Verify the installed version and a scoped read-only credential locally.

  3. Connect privately

    Use an approved private tunnel or authenticated HTTPS MCP service.

  4. Prove it in ChatGPT

    Discover tools and read a real repository, then cross-check the Forgejo UI.