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

Write the ADR for chat modes

Open Beginner friendly
  • Is something wrong?
#2,220 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@SakarPaisen is already working on this.

Since Oct 13, 2026.

  • #2244 by @SakarPaisen — open

Assessment

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

Research direction

Read docs/architecture/model-capabilities.md and the planned ADR 0044 entry in the file-agent README, then review the decision built in #2207 as described in the issue. Write an ADR under docs/adr/ explaining the chat-mode choices and why, and update or supersede the planned 0044 entry to match. Done when both documents reflect the stated decision.

Written by the indexing model from the issue text.

Description

architecture desktop documentation

No ADR records the chat-modes decision built in #2207:

  • Basic (Q&A) and Agentic are chosen per chat, and a chat keeps its mode.
  • No measured score keeps a model out of Agentic. Only technical gates do: no opencode, a stated no on tool calls, a stated window under 32,768 tokens.
  • The default is Agentic for a model measured at agent on a remote host, and Basic otherwise, local copies included.
  • A pass holds only where it was measured; expensive flagships are assumed.

The file-agent README's planned ADR 0044 ("What a model may do comes from a reviewed, measured capability manifest") describes the opposite of what was built, so it needs rewording or superseding. What is built is in docs/architecture/model-capabilities.md.

Done when: an ADR under docs/adr/ records the decision and why, and the planned 0044 entry matches it.

Dominant language
Python
Stars
16.3k
Forks
1.6k
Avg merge
11h 37m
Merged PRs (30d)
261

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 MODSetter/SurfSense

All issues in MODSetter/SurfSense

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.