Skip to content
CodexinfraWeb16 files · +361 −135

Audit, clean up, and deploy a Read-Along AI Gradio app to a Hugging Face Space

Session from read-along-ai-agent-traces on Hugging Face by kingkw1 · MIT · condensed by Coders Talk

1h 28msession
0interventions
GOAL

Audit the read-along-ai hackathon project against its evolving vision and eligibility rules, clean up docs/tests, then deploy the app as a Hugging Face Space and fix the runtime issues that came up.

  1. Prompt · +0
    Audit our docs, readme, and app against the hackathon vision and eligibility, including badges/awards; we dropped the multi-reading-level idea.
  2. Agent did · +0m
    Read README, specs, app.py, inference modules and tests; ran the light pytest suite (4 failures from stale output contracts); produced an audit summary of drift, eligibility, and repo size (16GB with GGUF models).
  3. Prompt · +11m
    Update spec docs and README for the sentence-only MVP, keep placeholders and Off the Grid/Llama Champion claims, and clean up stale tests into sensible folders.
  4. Agent did · +11m
    Moved tests into tests/, converted local smoke test to a manual script, updated docs/README/requirements to reflect the sentence MVP, split requirements-dev.txt, and fixed path/import breakage until pytest was green (32 passed, 2 skipped).
  5. Prompt · +37m
    Walk me through creating the Hugging Face Space and review hackathon submission guidelines before doing more UI tweaks.
  6. Fail · +41m
    git push to the Space remote was rejected, then HF CLI upload failed with 403 because the saved token only had read permission.
  7. Prompt · +42m
    Take this over yourself until you hit something only I can fix, like credentials.
  8. Agent did · +42m
    Diagnosed the credential wall, staged a vetted small upload folder (excluding .hackathon, models, caches) and, once a write token was supplied, pushed via hf upload successfully.
  9. Fail · +51m
    First Space build failed: Python 3.13 default plus pinned transformers/huggingface-hub versions conflicted with Gradio 6's requirements.
  10. Agent did · +52m
    Pinned python_version 3.12, made requirements lean and Modal-first, fixed local-vs-Modal prewarm routing, guarded missing Modal secrets, fixed a growing-whitespace CSS layout bug, iteratively re-uploaded and polled the Space until it ran cleanly, and built a reusable deploy_space.sh script as the standard upload shortcut.
  11. Break · 5h 09m away, not counted
  12. Outcome · +1h 28m
    Space build clean and RUNNING with a live Modal TTS smoke test passing; local suite at 36 passed, 2 skipped; repo restructured with a repeatable deploy_space.sh upload shortcut.
VERDICT

Next time I'd ask upfront for a deploy script instead of letting the agent hand-run git/HF CLI commands each time — that's what actually stabilized the workflow. The correction that mattered most was catching the read-only HF token and the Python 3.13/Gradio 6 dependency conflict; once those were fixed the Space just worked. I'd also front-load 'don't upload local model files or .hackathon notes' so I don't have to catch that mid-session.

I tried this · 0

Discussion · 0

How Builds work