Repo-native backend tool Orchestrator
GitHub repo → Fly.io backend → GitHub Pages frontend
Backend scaffold fly.toml Dockerfile GitHub Actions Pages wiring
GitHub repo slug owner/name
Used only for generated paths and comments. No network calls are made.
Fly.io app name fly apps create
Must match your Fly.io app. The tool wires URLs and config around this.
Backend base path folder
Relative folder inside the repo where backend code + Dockerfile will live.
Frontend base path folder
Relative folder for your static UI (served via GitHub Pages or any static host).
Backend language runtime
Generates a minimal API server wired for Fly.io.
Public API base URL frontend → backend
Used in the generated frontend config shim. You can override at runtime via env.
Optional notes / purpose comment
Idle · waiting for input No network calls
How to use: generate → copy each file into your repo → commit → push → run fly deploy.
File: backend/main.py /backend/main.py
Generated files will appear here. Fill in the inputs and click Generate repo-ready files.
Workflow: repo as source of truth · Fly.io as execution layer · Pages as UI surface All logic runs locally in this HTML file
🔍 Live GitHub Scanner detecting…
⚠ No token
The Service Worker backend makes real GitHub Code Search API calls. The GitHub PAT (AGENTR) is loaded automatically from the server — no manual configuration required.
Detecting backend mode…
Loading PAT from server…
Repos — Files — Markers — Pending — Confirmed —
Activity log — use buttons above to start scanning.