abbdbb2f87
* initial base memroy impl * update, add example with chromadb * include mimetype consideration * add transform method * update to address feedback, will update after 4681 is merged * update memory impl, * remove chroma db, typing fixes * format, add test * update uv lock * update docs * format updates * update notebook * add memoryqueryevent message, yield message for observability. * minor fixes, make score optional/none * Update python/packages/autogen-agentchat/src/autogen_agentchat/agents/_assistant_agent.py Co-authored-by: Eric Zhu <ekzhu@users.noreply.github.com> * update tests to improve cov * refactor, move memory to core. * format fixxes * format updates * format updates * fix azure notebook import, other fixes * update notebook, support str query in Memory protocol * update test * update cells * add specific extensible return types to memory query and update_context --------- Co-authored-by: Eric Zhu <ekzhu@users.noreply.github.com>
Building the AutoGen Documentation
AutoGen documentation is based on the sphinx documentation system and uses the myst-parser to render markdown files. It uses the pydata-sphinx-theme to style the documentation.
Prerequisites
Ensure you have all of the dev dependencies for the autogen-core package installed. You can install them by running the following command from the root of the python repository:
uv sync
source .venv/bin/activate
Building Docs
To build the documentation, run the following command from the root of the python repository:
poe --directory ./packages/autogen-core/ docs-build
To serve the documentation locally, run the following command from the root of the python repository:
poe --directory ./packages/autogen-core/ docs-serve
[!NOTE]
Sphinx will only rebuild files that have changed since the last build. If you want to force a full rebuild, you can delete the ./packages/autogen-core/docs/build directory before running the docs-build command.
Versioning the Documentation
The current theme - pydata-sphinx-theme - supports switching between versions of the documentation.
To version the documentation, you need to create a new version of the documentation by copying the existing documentation to a new directory with the version number. For example, to create a new version of the documentation for version 0.1.0, you would run the following command:
How are various versions built? - TBD.