You're trying a new CLI against a real GitHub repo.

Everything is fine until the tool says: create a personal access token.

Classic or fine-grained? Which permissions? Which repo access? Why did GitHub say 404 when the repo definitely exists?

That is the kind of moment where engineers stop trusting a setup flow.

That is the focus of imdone-cli 0.70.0: not adding more setup ceremony, but removing the places where GitHub setup made people guess.

The 0.70.0 GitHub setup path now gives direct token creation links, names the permissions imdone needs, calls out repository access for fine-grained tokens, supports SSH remote formats during setup and clone, and falls back to supported REST issue endpoints when GraphQL is not available to a fine-grained token.

The goal is not a prettier prompt.

The goal is to let you prove imdone with one real GitHub issue:

1. run imdone init and connect a real GitHub repo

4. inspect the local Markdown in backlog/current-sprint/

5. make one update

6. run imdone push

You should be able to see the value in one real workflow: run init, inspect an issue locally, update it, and push it back.

Try the GitHub setup path here:

https://imdone.io/imdone-cli/getting-started

And if there is still a setup step that makes you hesitate, reply and tell me where. Those moments are usually where the product needs to get clearer.

Jesse