Skip to content

Take Project Context & Personal Memory into Account #7

@vorburger

Description

@vorburger

This is an example of a (private) commit.

It (wrongly) generated "focusing on better integration with the Microservice Communication Protocol (MCP)."

So far, that's "normal" - because that repo at the time of that commit just used the term MCP - without defining it anywhere.

In this commit I've added a definition. But unless that line in that file was changed again, it still wouldn't "see" that. So what you ideally would want is to "have the entire repo in the context" - or have it use RAG.

Alternatively, and perhaps more easily and to start with, it would be neat if I could have e.g. a http://github.com/vorburger/ai-agents-memory sorta repo, where I would maintain a MEMORY.md kinda file, where I would write `MCP is the Model Context Protocol, see https://modelcontextprotocol.io" - and then simpy point any agents that I run to that! (Enola itself does not have a Command Line argument feature flag for doing that just yet, but it shouldn't be very hard to add it.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions