F-027 A10 — Connect AI order and labels in Settings (rest of #410)
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Rest of #410 (slice A10 of F-027, founder direction 2026-10-09, contract PR #401). Carries every part of #410 that its first pull request (the launcher part, issue #410) does not deliver. #410 stays open until this issue and that pull request are both accepted.
Depends on. #277: the Connect AI section on claude-hubert/279-claude-signin (PR #398, gated by #331/#385). Nothing here starts before that section is on main; this slice amends it (order and labels), it does not rebuild it.
Remaining scope (unchanged from #410 and AST-1)
Verbatim from AST-1:
-
Order on Connect AI (Settings → Agents and AI, #277). When the instance has
the runtime on, the first two choices are Sign in with Claude and Sign in with
ChatGPT. They open the guided sign-in below. Use an API key and the other
providers sit under Other ways to connect. When the runtime is off, the page says
so in one sentence and shows the API key choices; nothing on Home or in the set-up
sheet then promises "the plan you already have". -
Plain account labels. "Claude · your subscription", "ChatGPT · your
subscription", "Anthropic Console · API billing", "OpenAI · API key". The F-022
payer labels stay as the longer text in the account row (AIM-4 explicit payer). -
"Which account should I use?" One folded line on Connect AI, in plain words:
- "Claude Max and Team plans include monthly API credits. Anthropic recommends an
API key for work that runs on its own, and a key from your Claude Console
organization uses those credits (about 5 minutes in the Claude Console)."
(support 17154008, research §3.1) - "Using Flux for work? In the EU and Switzerland, Claude's personal plans (Pro,
Max) are for non-business use. A Team plan or an API key covers work." (Consumer
Terms §11, EEA text)
- "Claude Max and Team plans include monthly API credits. Anthropic recommends an
Acceptance (copied from AST-1)
- AST-1.1 With the runtime on, Connect AI lists Sign in with Claude and Sign
in with ChatGPT first, and the API key choices only under Other ways to
connect (Playwright, both widths). - AST-1.2 With the runtime off, the page shows one plain sentence and the API
key choices; no sign-in button is shown (Playwright).
The same slice table lists one more A10 item that is neither the launcher nor the Connect AI page: "AST-2.1, AST-2.4 | A8 (sign-in refusal on paid hosting: A10)". The launcher has no paid-hosting setting (the first pull request says so); AST-2.4's "With paid hosting set, runtime sign-in, jobs and reactions on a subscription are refused with one plain sentence (app test)" stays to be delivered here or confirmed with the AST-2 owner once a paid-hosting setting exists.
Files and tests
app/apps/web/src/Connect AI section (#277 branch).- AST-1.1 and AST-1.2 as Playwright (
scripts/check_ui.sh), at both widths, against the final design (Prostota) components and in dark mode; the UI is reviewed against F-027's journeys by an independent evaluator in the running app. - Rules: Docker tests with fakes/mocks only (no real vendor account, key or spend).
Covered by the first pull request of #410 (under review; not repeated here)
AST-1.3 and AST-1.4 (the launcher question in ./flux up and ./flux ai on, the host checks, the statement line), and the operator guide docs/operations/agent-runtime.md.
Owner: claude-maurycy.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 14h 40m
- Merged PRs (30d)
- 242
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ColdPhase/flux
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
WebKit: scenarios test_1 intermittently fails adding the next person (status keeps the previous name); test_2 skippedPossibly taken @Zamojski5 claimed this today. Open
ColdPhase/flux#491 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Bayern feature:Application ready web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
digitalfabrik/entitlementcard#3176 ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NanmiCoder/cc-haha#1533 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
🐛 Bug: Calendar work items cannot be opened on mobilePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100