[l2ysho]

Note

apify runs ls outside an Actor project failed with "Unable to detect what Actor to create a build for" — a builds message on a runs command. The shared fallback now names no operation and says what to do.

Before

$ apify runs ls
Error: Unable to detect what Actor to create a build for. Please run this command in an Actor directory, or specify the Actor ID.

After

$ apify runs ls
Error: No Actor specified. Pass an Actor ID or "username/name", or run this command from an Actor project directory.

Changes

• resolveActorContext is shared by runs ls, builds ls, builds create and actors info, so its generic fallback can't name one operation. Rewritten.
• The four callers each appended their own hint. It duplicated the new copy, and on the "not found" branches it was wrong advice — the user did pass an ID, so changing directory wouldn't help. Removed.
• Copy-only. No logic, no flags, no exit codes. update-docs produces no diff.

Notes

• Pre-existing and out of scope, found while reviewing these lines: all four commands exit 0 on this failure, and three write the error to stdout, which breaks --json. Separate PR.
• actors info can't reach the fallback — its actorId arg is required. The edit there only affects the "not found" branches.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/apify-cli@1563

commit: c4efc81

[apify-factory]

Looks good, nothing blocking.

🏭 Apify Factory auto approved ✅ — every gate opened, nobody had to knock

Every gate passed, and neither the reviewer nor a juror found anything a human needs to look at.

_{Approval locked to c4efc81f1 · workflow run}