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

Docs list three task-page session controls that no longer exist

Open Beginner friendly
#147 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python, react
Domain
documentation

Research direction

Read docs/site/tasks-and-agents.md and docs/site/troubleshooting.md, comparing their session-control descriptions with website/src/TaskPage.jsx. Update both pages to describe only the available control, “Save and end session,” then check that the specified grep finds no obsolete control names. Run cd website && npm run build:docs and include the generated site/docs/ changes.

Written by the indexing model from the issue text.

Description

documentation good first issue

The task page's session controls were reduced to one way out: Save and end session (website/src/TaskPage.jsx). The docs still describe the old ones.

Where:

  • docs/site/tasks-and-agents.md (the controls table): Give new prompt, Pause & save, Stop session
  • docs/site/troubleshooting.md: "Stop session ends the process and deliberately changes nothing else…"

Done when both pages describe only controls the task page has, with "Save and end session" as the way to end a session, and grep -n "Stop session\|Pause & save\|Give new prompt" docs/site/*.md finds nothing.

After editing docs/site/*.md, run cd website && npm run build:docs and commit site/docs/ with it, or CI's build-web fails.


Getting started: pip install -e ".[dev]", then python -m pytest -q (offline). UI work: cd website && npm ci && npm test (Node 22). See CONTRIBUTING.md. One small PR with the change (and its test, where there is one) is perfect.

Dominant language
Python
Stars
116
Forks
22
Avg merge
13h 39m
Merged PRs (30d)
51

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 ldbumble/taskuary

All issues in ldbumble/taskuary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.