Livekit integration

[paul-paliychuk]

Important

Introduces Zep LiveKit integration with dual agent architecture for persistent memory in voice AI applications, including examples and comprehensive documentation.

• Integration:
  • Adds zep_livekit integration for LiveKit, providing persistent memory capabilities.
  • Implements ZepUserAgent for thread-based memory and ZepGraphAgent for graph-based memory in agent.py.
• Features:
  • Supports event-driven architecture for automatic conversation capture.
  • Provides message attribution and hybrid memory retrieval.
  • Includes error handling, type safety, and minimal logging.
• Examples & Documentation:
  • Adds voice_assistant.py and graph_voice_assistant.py examples.
  • Comprehensive documentation in README.md and CLAUDE.md.
• Development & Infrastructure:
  • Includes Makefile for development workflows.
  • pyproject.toml specifies dependencies and configurations.
  • CHANGELOG.md documents version history.

^{This description was created by for ca800bf. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 1c7e754 in 2 minutes and 31 seconds. Click for details.

• Reviewed 1503 lines of code in 11 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. integrations/python/zep_livekit/README.md:24

• Draft comment:
  Usage example inconsistency: The README imports 'ZepMemoryAgent' and 'ZepAgentSession', but the module actually exports 'ZepUserAgent' (and 'ZepGraphAgent'). Update the example for consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% Since this is a new README file, I need to be careful about assuming the commenter is correct about the actual class names. The README appears to be carefully written with consistent class names throughout - ZepMemoryAgent appears multiple times including in the API reference section. Without seeing the actual module code, I cannot verify if there truly is an inconsistency. I could be wrong about which class names are correct - maybe the commenter has access to the actual module code that I can't see. The README could be the one that's wrong. While that's true, the README shows remarkable internal consistency in using these class names, including detailed API documentation. It seems more likely that the README is correct and the commenter may be mistaken. Without being able to verify the actual module exports, and given the internal consistency of the README, this comment should not be kept as we lack strong evidence that it is correct.

2. pyproject.toml:5

• Draft comment:
  Python version inconsistency: The integration's pyproject.toml requires Python >=3.10, but the root pyproject.toml requires >=3.12. Consider aligning these requirements.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

3. integrations/python/zep_livekit/CLAUDE.md:134

• Draft comment:
  Typo noticed: The model name 'gpt-4o-mini' might be a typo. Did you mean 'gpt-4-mini'?
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_IMGDISzMGAVSDmeC

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed b1ef225 in 1 minute and 22 seconds. Click for details.

• Reviewed 1011 lines of code in 5 files
• Skipped 0 files when reviewing.
• Skipped posting 6 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. integrations/python/zep_livekit/CHANGELOG.md:61

• Draft comment:
  Consider appending a newline at the end of the file to comply with POSIX standards.
• Reason this comment was not posted:
  Comment was on unchanged code.

2. integrations/python/zep_livekit/examples/graph_voice_assistant.py:32

• Draft comment:
  Logging is set to DEBUG level; confirm that this logging level is intended for production or consider adjusting it.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

3. integrations/python/zep_livekit/src/zep_livekit/agent.py:80

• Draft comment:
  Consider adding explicit type annotations for the 'event' parameter in the session event handler to improve clarity and type safety.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

4. integrations/python/zep_livekit/src/zep_livekit/agent.py:138

• Draft comment:
  Consider using logger.exception() in exception handlers to capture full stack traces for debugging, instead of logger.warning().
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. integrations/python/zep_livekit/src/zep_livekit/agent.py:310

• Draft comment:
  Similarly, in ZepGraphAgent's _store_assistant_message, consider using logger.exception() for more detailed error logging.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

6. integrations/python/zep_livekit/src/zep_livekit/agent.py:344

• Draft comment:
  Slicing user_text to 400 characters is arbitrary; consider defining a named constant for the query length limit to improve clarity and maintainability.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_HgKeGbJeSyY6nMSD

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed 329f83f in 2 minutes and 6 seconds. Click for details.

• Reviewed 173 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/release-integrations.yml:15

• Draft comment:
  Added the 'livekit' option. Ensure its naming matches the integration directory (zep_livekit) for consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. integrations/python/zep_livekit/README.md:291

• Draft comment:
  The Production Deployment section has been removed. Confirm that this removal is intentional and that users don’t need deployment guidance.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

3. integrations/python/zep_livekit/README.md:203

• Draft comment:
  The Agent Comparison table header has been updated to 'Memory Access Method'. Verify that the updated descriptions accurately reflect the integration’s behavior.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_Y9AsRNJb7jPskj67

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed df0218b in 39 seconds. Click for details.

• Reviewed 14 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. integrations/python/zep_livekit/README.md:304

• Draft comment:
  Removed extraneous LiveKit resource links. Ensure that this removal aligns with the updated integration documentation.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_So5MFpi3LWn5CEs0

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed ca800bf in 39 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. integrations/python/zep_livekit/README.md:185

• Draft comment:
  Graph id updated to 'company_knowledge_base'. Ensure this change aligns with the intended setup in the Direct Graph Memory Access section for consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_hOMiPgu4ZREpwurX

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}