Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

F-027 A7 — The assistant screen and the journeys

Open
  • Is something wrong?
#407 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 9, 2026.

Assessment

This issue has not been assessed yet.

Description

Slice A7 of F-027 (founder direction 2026-10-09; contract PR #401). The AST criteria referenced below are defined there and are this issue's acceptance criteria.

  • Scope. AST-10's one screen on computer and phone; the panel (Now, Recent, Can,
    Message, ⋯ Pause my assistant); the Can sentence shared with the hand-off
    picker (#347) and the agent page; Jonas's hand-off to Ada's assistant as a Needs-you
    item for Ada (AST-3.5); message headers with the AI company and the Agents tab policy
    row (AST-3.6); Message and ⌘K opening a conversation with the assistant mentioned;
    the Home set-up card and the @ entry; suggestions only where the assistant is a
    member; offline states; the New-tool line (AST-3). Grows with A3/A4 (waiting and
    run messages), A8 and A9 (their parts).
  • Files. app/apps/web/src/assistant/AssistantSettings.tsx (replaced by the
    screen), app/apps/web/src/assistant/assistant.css (final tokens only), the
    hand-off, agent panel, composer and Home greeting components.
  • Tests. AST-3.5, AST-3.6, AST-4.1 and AST-5.1 (screen), AST-10.1, AST-10.2,
    AST-10.4 to AST-10.6, AST-10.8 to AST-10.11, AST-10.14, AST-10.15 in Playwright
    (Chromium and WebKit, both widths, light and dark); axe; AST-10.12 independent UX and
    neutral visual review.
  • Depends on. A1; #350's Settings layout (merged) and #347/#344/#343 components.

Rules: Docker tests with fakes/mocks only (no real vendor account, key or spend); final design (Prostota) components; UX reviewed against F-027's journeys by an independent evaluator in the running app.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
13h 27m
Merged PRs (30d)
224

Getting set up

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.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.