Skip to content

fix(cli): name the GitHub rate limit on a direct run - #135

Merged
harlan-zw merged 2 commits into
mainfrom
fix/direct-rate-limit
Sep 7, 2026
Merged

fix(cli): name the GitHub rate limit on a direct run#135
harlan-zw merged 2 commits into
mainfrom
fix/direct-rate-limit

Conversation

@harlan-zw

Copy link
Copy Markdown
Collaborator

❓ Type of change

  • 📖 Documentation
  • 🐞 Bug fix
  • 👌 Enhancement
  • ✨ New feature
  • 🧹 Chore
  • ⚠️ Breaking change

📚 Description

--direct sends anonymous requests to GitHub, so a shared machine burns the 60 per hour quota fast. When it does, the CLI blames the wrong service and gives no wait:

$ skilld run github:tt-a1i/archify/archify --direct
SERVICE_UNAVAILABLE: the remote service returned HTTP 403

Now:

RATE_LIMITED: GitHub rate limited this request. Retry after 2843 seconds.

The update comparison path already recognised this response; direct runs and restores now do too.

🤖 AI disclosure: Harlan Agent Kit modified this description. My AI open-source policy.

https://claude.ai/code/session_01ASGK6drkuCbo7vsPQcYCvn

An exhausted anonymous GitHub quota surfaced as
"SERVICE_UNAVAILABLE: the remote service returned HTTP 403". That blames
skilld.dev for a GitHub limit and gives the user nothing to act on.

A rate limited GitHub response is now RATE_LIMITED and names the wait
from x-ratelimit-reset or retry-after, matching the update comparison
path that already recognised it.

Claude-Session: https://claude.ai/code/session_01ASGK6drkuCbo7vsPQcYCvn
@harlan-zw
harlan-zw merged commit dc7a326 into main Sep 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant