Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature]: Easier for a new user/developer to play.

Aperta
#423 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
docker, docker-compose, git, markdown, python

Direzione di ricerca

Start with the README, which the issue says does not explain how to use ingested memories, and compare it with the guidance in EverMe. Then inspect the ingestion formats and the aagentic_retrieve entry point in everalgo, both named in the issue. The requested outcome spans onboarding, source-based development, Docker, and benchmarks, so first clarify which of these is in scope and how each should be verified.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Area

developer experience

Problem or opportunity

A brilliant project. Something might make it more popular.

  1. Before applying EverOS, what should I do if I want to memorize things accross the agents like Claude code, Codex, Gemini CLI, Cursor and Slack etc,. They all can export conversations.

everos ingest ~/chats/
  1. After ingesting the exiting data, then, I want to use those memo in ClaudeCode/Codex/Cursor. How?
    I didn't find it in README.md. But, I happenly find it in EverMe(I believe many people can't find it).
    It's brilliant in term of software architecture. But for convenience for a user/developer, cloning once for everything will be better.
    Maybe submodule in git might make it work in both ways.

  2. What if I want to start the server by souce code instead of installing anything, what I'm going to do?
    I want to print things while aagentic_retrieve which is in everalgo, another project. How could I apply my alteration in it?
    Can it be done less than 3 steps? Maybe it can, show me please.

  3. It will be thankful if a clean and complete eviroment(maybe docker image) is provided.
    What I'm suppose most developer would do is like following:

    • Apply docker compose up to start a server
    • Change code in the container and docker restart to apply the latest alterations.
    • Otherwise, I need to install a lot of packages and debug the envirement.
  4. About benchmarks, astonishing!! They should be shown in readme.md, which is much easier for researcher to find it.

Proposed solution
  • Ingestion supports five chat formats automatically:

    • Claude JSON exports
    • ChatGPT exports
    • Slack exports
    • Markdown conversations
    • Plain text transcripts
  • Others as I suggested.

Alternatives considered

No response

Additional context

No response

Lingua principale
Python
Stelle
13.3k
Fork
926
Merge medio
17h 8m
PR unite (30g)
32

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EverMind-AI/EverOS

Tutte le issue di EverMind-AI/EverOS

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.