zai-org / zai-org/feedback

[Bug] Connect account does not work

Open
#699 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: Bug
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

账号 / 登录 · Account / Login

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

阻塞使用 · Blocking (无法使用核心功能 / core function unusable)

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

I am using ZCode App on Linux. Upgraded to latest version 3.12.3. The 'Connect' feature does not work.

I am using a Team Plan.

Personal Plan is not subscribed.

Using API key is a workaround.

复现步骤 · Steps to reproduce
  1. Open ZCode
  2. Press 'Connect'
  3. Authenticate in browser - Success
  4. ZCode App shows "Login failed, please try again"
期望表现 · Expected behavior

Connect should work.

实际表现 · Actual behavior

Login failed, please try again

ZCode 版本 · ZCode version

3.12.3

设备 / 系统 / 浏览器 · Device / OS / Browser

Linux / Firefox

截图 / 录屏 / 日志 · Screenshots / Recordings / Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Connect flow in ZCode 3.12.3 on Linux with Firefox: launch Connect, complete browser authentication, and observe the app's login-failed result. Trace the account/login flow from the Connect entry point and compare the successful browser step with the app response. Done means Team Plan users can complete Connect without the login-failed message; API-key use should remain unnecessary.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
authentication, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.