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

Inbox "Needs you" is the one queue, Home shows the top three, and the Decisions view goes

Open
  • Is something wrong?
#342 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 8, 2026.

  • #372 by @PelikanFix16 — open
  • #393 by @PelikanFix16 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python, react, typescript
Domain
backend, frontend, testing

Research direction

Start with the pinned design guide at docs/design/final/README.md, especially §§1 and 5, then inspect the listed entry points under app/apps/web/src: notifications/InboxView.tsx, app/views.tsx, returns/SinceYouLeft.tsx, and app/HomeTasks.tsx. Rewrite the named tests in app/tests/ui and run ./scripts/check_ui.sh; run ./scripts/check_application.sh when API or data paths change. Done means the acceptance criteria work across desktop and mobile, with keyboard, touch, accessibility, and visual checks; coordinate dependencies #338, #340, and #341 first.

Written by the indexing model from the issue text.

Description

agent:ready enhancement

Part of #336 (F-026, founder direction 2026-10-07). Design guide: docs/design/final (§5 behaviour · §1 principles; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".

Outcome

Everything that needs a person (decisions, agent questions, blockers and mentions) is in one Inbox. Home shows the top three and where to continue. There is no Decisions view or archive.

Final design

desktop-inbox phone-inbox desktop-home phone-home

Acceptance criteria

  • AC-1. Inbox lists decisions, agent questions, blockers and mentions across projects, with the filters All · Decisions · Questions · Blocked · Mentions. Each item opens in the detail panel or sheet.
  • AC-2. Done (E), Not now (S) and Accept (A) apply at once and show a toast with Undo (Z). Not now asks when it returns: tomorrow, next week, or when a task is done (S11).
  • AC-3. A decision is one card on both devices (P4): "Proposed decision", "Needs you", the reason, what it is based on, then Accept / Not now / Discuss. It shows who has accepted and who is still waiting.
  • AC-4. Home shows the Continue where you left off card (P1: the whole card is clickable, with a round arrow), the top three Needs you items, and a working agent with Stop.
  • AC-5. The Decisions view, its archive and their routes are removed. Old links redirect to the Inbox Decisions filter or to the decision itself, and no decision, access rule or history is lost.

What changes in the code today

From a read of main at 3c553b79; the owner confirms before starting. Paths are under app/apps/web/src, public/ is app/apps/web/public, root scripts/ and tests/ are the repository's, and UI tests are in app/tests/ui.

Change

  • notifications/InboxView.tsx (New/Earlier lists, unread dot, Mark as read) → the Needs you queue with filters, Done / Not now / Accept and Undo.
  • Home (app/views.tsx, returns/SinceYouLeft.tsx, app/HomeTasks.tsx) → Continue card (P1), top three Needs you, working agent. The return contract (F5) stays: its data feeds the Continue card and the "Since you left" line in the conversation (S7).
  • returns/WhatMatters.tsx recap panel folds into Inbox and Home; its "Needs you" counting (returns/useNeedsYou.ts) is reused.
  • ui/Toast.tsx: add an action button (Undo) and Z.

Remove

  • "Decisions & results" in the Tasks toolbar and the Decisions/Results groups (work/ProjectTasks.tsx). A decision's history (earlier rules) stays reachable from the decision's detail panel; results show in their task's details.

New

  • Snooze with return choices (tomorrow, next week, when a task is done) — needs a server field and API.
  • Who has accepted / who is waiting on a decision card.

Tests to rewrite

  • test_tasks_board.py (Decisions & results), test_work_decisions.py, test_decision_authority.py, test_notifications.py (dot, Mark read), test_return_view.py (05, 06*, 07b, "I have the context"), test_scenarios.py.

Depends on

#338, #340, #341 (tokens and shared components first; independent parts can start earlier).

Related: #238 (draft PR #244 and preserved decoupled implementation) undoes an unused AI-created task under AC-U1–U5 and is required in v0.1 by founder direction, 2026-10-07; the Undo here independently covers this issue's quick actions. Neither outcome is satisfied by the other.

How to test

./scripts/check_ui.sh            # browser suite; add the new or changed tests
./scripts/check_application.sh   # when API or data paths change
python3 scripts/check_agent_setup.py && git diff --check

Compare with the renders above at 1440 × 900 and 390 × 844 CSS px, in light and dark, on ./flux demo data, then get an independent visual review with a neutral brief (guide §9). Screenshots do not prove interaction or accessibility, so also test keyboard, touch (Chromium and WebKit emulation), reduced motion and contrast in the running app.

Owner: whoever claims it (assign yourself and comment once). Evaluator: the other agent. The design is a founder direction: implement it as drawn; raise a conflict with a functional contract on #336 instead of changing the design.

Updated 2026-10-07: cross-link to #238 (Undo) added.

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.