[l2ysho]

Draft for #1299

Open questions

Q1: apify create suggests apify run for standby templates

apify create my-actor -t ts-standby ends with Next steps: … apify run. The template sets usesStandbyMode: true, so the command that runs it the way the platform does is apify run --standby. apify run now prints a hint pointing to --standby, but create sends the user to the wrong command first. buildNextSteps() always pushes apify run (create-utils.ts#L95).

Important

Should create suggest apify run --standby when the created Actor has usesStandbyMode: true?

Q2: server status shows pool settings to callers of multi-tenant Actors

For a multi-tenant Actor, status prints Memory, Idle timeout and Requests/run in the same form as for a single-tenant Actor. For single-tenant they decide the caller's cost: runs start in the caller's account, and the caller can override them with a task. For multi-tenant they describe the developer's pool: the caller pays per event only and cannot change them, because tasks do not work with multi-tenant Actors. When the caller owns the Actor, they are exactly what the owner pays for.

Important

• Hide the lines for multi-tenant Actors unless the caller owns the Actor ?
• Keep them under a label: Pool (developer's account):, or Pool (your account): for the owner ?
• Leave as is ?

Related: for multi-tenant Actors, status skips the run lookup. The owner could see the pool runs (standby.deployment: MULTI_TENANT_*); a caller cannot.

Manual test

Published ts-standby template (single-tenant)

$ apify create server-poc-official -t ts-standby
$ cd server-poc-official
$ apify run
Info: This Actor has a server interface ("usesStandbyMode" in actor.json). Pass --standby to run it the way the platform does for HTTP requests.

$ apify run --standby
Success: The Actor server is ready at http://localhost:4321

$ curl http://localhost:4321/
Hello from Actor Standby!

$ apify push
…
Server interface URL: https://<username>--server-poc-official.apify.actor
Send a request: apify server request <username>/server-poc-official /

$ apify server status
URL:            https://<username>--server-poc-official.apify.actor
Tenancy:        single-tenant (runs in your account "<username>", which pays the platform usage)
Build:          latest (0.0.1)
Memory:         1024 MB
Idle timeout:   300 s
Requests/run:   3 desired, 4 max
Endpoints:      not documented (see the Actor README)
Runs:           none running; the next request starts one (cold start)

$ apify server endpoints
Info: Actor "<username>/server-poc-official" does not document its endpoints. See its README: apify actors info <username>/server-poc-official --readme

$ apify server request /
Info: <username>/server-poc-official is single-tenant: it runs in account "<username>", which pays the platform usage.
Info: Waiting for the Actor. If no run is ready, the platform starts one, which can take up to 2 minutes.
Hello from Actor Standby!

$ apify server status
…
Runs:           1 running (<runId>); the next request is served warm

$ apify call --input '{bad'
Info: <username>/server-poc-official also has a server interface. To send it HTTP requests instead of starting a run, use "apify server request <username>/server-poc-official <path>".
Error: Cannot parse JSON input.

Updated ts-standby template (containerPort, webServerSchema; separate actor-templates change)

$ apify run --standby
Success: The Actor server is ready at http://localhost:4321

$ apify push
…
ACTOR: Found web server schema referenced from .actor/actor.json
…
Build: SUCCEEDED

$ apify server endpoints
GET     /  Return a greeting

$ apify server request /
Info: <username>/server-poc-updated is single-tenant: it runs in account "<username>", which pays the platform usage.
Info: Waiting for the Actor. If no run is ready, the platform starts one, which can take up to 2 minutes.
Hello from Actor Standby!

Rejected before sending

$ apify server request //evil.example/x
Error: The path "//evil.example/x" points outside https://<username>--server-poc-updated.apify.actor. Pass a path on the Actor's server.

$ apify server request '/?token=abc'
Error: Do not put the API token in the URL. The CLI sends it in the Authorization header.

Multi-tenant (apify/web-fetch)

$ apify server status apify/web-fetch
URL:            https://web-fetch.apify.actor
Tenancy:        multi-tenant (runs in the developer's account; you pay per event)
Build:          latest (0.0.30)
Memory:         1024 MB
Idle timeout:   300 s
Requests/run:   8 desired, 10 max
Endpoints:      2 documented (apify server endpoints apify/web-fetch)

$ apify server request apify/web-fetch / -p '{"url":"https://example.com"}'
{"url":"https://example.com/","fetch":{"loadedUrl":"https://example.com/","httpStatusCode":200,…},"markdown":"This domain is for use in documentation examples without needing permission. …"}

🤖 Generated with Claude Code

[apify-factory]

Looks good, nothing blocking.

🏭 Factory review — ℹ️ not auto-approved

This change was reviewed but cannot be auto-approved: a gate failed, so the review cannot end in an approval.

check	result
Static gates	❌ 12/16 — pr-open-and-ready, max-files, max-lines, no-risky-content
Review findings	✅ none
Reviewer escalation	❌ Adds a new public apify server command group that sends the user's API token to Actor-controlled standby hosts and changes run/push runtime behavior, with open design questions still listed in the PR.
Juror 1 — claude-sonnet-5-5, adversarial	⏭️ skipped — a gate failed

Why it was not auto-approved

Failed gates:

• pr-open-and-ready: PR is a draft
• max-files: 14 changed files, limit 10
• max-lines: 1325 changed lines (+1223/-102), limit 200
• no-risky-content: src/commands/run.ts: network call (network-call); src/commands/server/request.ts: network call (network-call); src/lib/server-actor.ts: network call (network-call)

The comments above are the review itself; this section only explains the approval decision. Push a change and request @apify-factory again to re-run it, or ask a human to review.

_{Reviewed 0c39d9eb3 · workflow run}

[l2ysho]

This is a quick draft of server actors support of CLI.

• 2 open questions worth to discuss
• Manual test section show how UX looks like so far (simplified copy pasta from my terminal)

@DaveHanns @patrikbraborec @jancurn pls take a look and let me know if you see some UX problems from user point of view (naming/flow)

[patrikbraborec]

Hi, thanks! One thing, we want to get rid of standby naming. Let's rename the following command:

apify run --standby

Ideally something like:

apify run --server-actor

The best thing would be that the CLI recognize the server actor, ie based on usesStandbyMode, and it automatically.