Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Two-step device code login for environments that cannot wait for approval (login and add --connect-cloud)

オープン
  • 何か問題がありますか？
#858 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
authentication, cli

調査の方向性

Start by reading the CLI entry points for rsconnect login and rsconnect add --connect-cloud, then trace the device-code polling and credential-storage flows named in the issue. Determine how pending state can be stored with owner-only permissions and resumed safely; done means both targets support a machine-readable start/finish flow that preserves valid codes and removes expired or denied ones.

索引モデルが issue の本文から書いたものです。

説明

cloud enhancement

Problem

Some agent environments run each shell command as a short call. Claude Cowork is one example:

  • A call ends after about 3 minutes.
  • The agent sees the output only when the call ends.
  • Child and background processes stop when the call ends.

rsconnect login --use-device-code and rsconnect add --connect-cloud print the verification URL and code, then poll for approval in the same process.
In these environments, the agent sees the code only after the call ends, which is too late to show it to the user.
The polling process then stops, so the login can never finish.

The device code flow is the correct flow for these environments, because it needs no localhost callback.
#842 asks rsconnect to fall back to the device code flow when the browser callback fails.
This issue asks for the next step: a device code login that works when the CLI cannot wait for approval.

Requested behavior

Split the device code flow into two commands. Each command exits immediately, or after a bounded wait.

# Posit Connect
rsconnect login https://connect.example.com --use-device-code --no-wait
#   prints the verification URL and user code, saves the pending login, exits
rsconnect login --finish [--timeout 120]
#   polls for up to --timeout seconds, then saves the credential like a normal login

# Posit Connect Cloud
rsconnect add --connect-cloud --account myteam --name cloud --no-wait
rsconnect add --finish [--timeout 120]

The flag names are only suggestions. Requirements:

  1. Save the pending login in the rsconnect-python config directory with owner-only permissions (0600). Never print the device code.
  2. If start runs again for the same target while a code is still valid, print the same link and code. Do not request a new code.
  3. Make the result machine-readable, for example a status word on the first line or distinct exit codes: pending (run finish again), failed (start again), or done.
  4. Keep the pending login while the code is still valid. Remove it when the code expires or the user denies it.
  5. Support both Posit Connect (login) and Posit Connect Cloud (add --connect-cloud).

Current workaround

We ship helper scripts in a Posit deploy skill for Claude Cowork that do this split with rsconnect-python internals.
For Posit Connect, they use rsconnect.oauth._poll_for_device_token, _unwrap_json_response, discover_oauth_metadata, register_client, keyring_store_token, and ServerStore.set.
For Posit Connect Cloud, they also use connect_cloud.urls, connect_cloud.client_id, connect_cloud.SCOPE, and connect_cloud.store_credentials_in_keyring.
The scripts work with 1.31.1, but private functions can change in any release.
A supported mode would let us remove the scripts.

The R rsconnect::connectCloudUser() has the same problem, but that belongs in the R package.

主要言語
Python
スター
38
フォーク
28
平均マージ
10時間 32分
マージ済み PR（30日）
7

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

posit-dev/rsconnect-python のほかの issue

posit-dev/rsconnect-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。