Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#423 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
docker, docker-compose, git, markdown, python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
13.3k
Forks
926
Merge medio
22 h 56 min
PR fusionados (30 d)
27

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de EverMind-AI/EverOS

Todos los issues de EverMind-AI/EverOS

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.