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

feat(*): Easier for a new user/developer to use

Open
#377 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
docker, python
Domain
ai, cli, devops, frontend, search

Research direction

No file, test, or entry point is named. Start by mapping the existing CLI/TUI and ~/.raven/config.json handling, then review how MCP servers, chat channels, memory, and research are currently configured. The proposal is complete only when its intended scope, implementation area, and acceptance criteria are clarified.

Written by the indexing model from the issue text.

Description

Problem
  1. TUI is advanced. If a GUI is provided, the bar of user will be reduced.
    Like OpenClaw/CherryStudio, a control UI(a WEB UI) is very friendly for a user/developer.
    So, the items in ~/.raven/config.json should be configured via a control UI.

    • LLM provider and model
    • A local working directory
    • MCP servers
    • Chat channels
    • EverOS long-term memory
    • Deep Research
    • Sandbox or execution location
  2. Terminal installation is advanced. If a docker image is provided, a lot of exceptions will be avoided.
    An indepenent experimental eviroment is crucial for a developer. It's really nice for us to provide one.

  3. What about adding a benchmark(borwseComp) for local file search/digestion.
    The deep research is porvided as a third-party service invocation tool. A good local files(MD/TXT) content deep understandig is also very useful.

Proposal

Already included.

Alternatives considered

No response

Area

CLI / TUI

Additional context

No response

Dominant language
Python
Stars
4.1k
Forks
94
Avg merge
10h 2m
Merged PRs (30d)
376

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 EverMind-AI/Raven

All issues in EverMind-AI/Raven

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.