openclaw - 💡(How to fix) Fix `openclaw models auth login` requires TTY; can't be scripted [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75793Fetched 2026-05-02 05:30:02
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
2
Timeline (top)
commented ×2closed ×1

Error Message

$ echo "AIzaSyC..." | openclaw models auth login --provider google --method api-key --set-default Error: models auth login requires an interactive TTY.

Code Example

$ echo "AIzaSyC..." | openclaw models auth login --provider google --method api-key --set-default
Error: models auth login requires an interactive TTY.
RAW_BUFFERClick to expand / collapse

For users wanting to provision providers via Ansible, scripts, or remote provisioning, the auth-login flow requires interactive TTY:

$ echo "AIzaSyC..." | openclaw models auth login --provider google --method api-key --set-default
Error: models auth login requires an interactive TTY.

This forces hand-editing auth-profiles.json (which has an internal schema users must reverse-engineer from dist/store-*.js) for any non-interactive provisioning.

Proposed fix: add --api-key <KEY> (and analogous flags for token/oauth) to allow non-interactive provisioning. Document the flag clearly in the CLI help.

extent analysis

TL;DR

Adding a non-interactive flag, such as --api-key <KEY>, to the openclaw models auth login command may allow for automated provisioning without requiring an interactive TTY.

Guidance

  • The error message indicates that the current implementation of openclaw models auth login requires an interactive TTY, which is not suitable for automated provisioning via Ansible, scripts, or remote provisioning.
  • To verify the issue, try running the command with the proposed --api-key <KEY> flag, if available, to see if it bypasses the interactive TTY requirement.
  • Consider documenting the proposed flag clearly in the CLI help to ensure users understand how to use it for non-interactive provisioning.
  • If the proposed fix is not yet implemented, users may need to continue hand-editing auth-profiles.json as a temporary workaround.

Example

No code snippet is provided as the issue does not contain sufficient information to generate a concrete example.

Notes

The proposed fix assumes that adding a non-interactive flag will resolve the issue, but the actual implementation details are not provided in the issue.

Recommendation

Apply workaround: hand-edit auth-profiles.json until the proposed --api-key <KEY> flag is implemented, as it is the most straightforward solution given the current information.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix `openclaw models auth login` requires TTY; can't be scripted [2 comments, 2 participants]