Relative paths incoherencies in agents definitions

[aheritier]

RAG setup requires to define where to look for docs and where to put the database

https://docs.docker.com/ai/cagent/rag/

AFAICS (also visible in samples like https://github.com/docker/cagent/blob/main/examples/rag/semantic_embeddings.yaml) these paths must be related to the agents file path but it's not explained in docs.

[aheritier]

Agents can be executed with cagent run some/path/to/agents.yaml but also as cagent run agentcatalog/pirate if I push the agents definition in a registry. In such case the base folder won't be the same? In the first case paths will be computed from the some/path/to/agents.yaml while in the second they'll be computed from .?

[aheritier]

Surprisingly the memory tool also uses relative paths related to the agent definition file BUT it cannot go outside of the current folder thus if I have my agent defined in .cagent/team.yaml with

      # Built-in toolset with configuration
      - type: memory
        path: ../data/memories.db

I get an error because the memory tool isn't not authorized to access to this folder