Skip to content

feat(examples): add Claude memory plugin example for OpenViking#246

Merged
MaojiaSheng merged 1 commit intovolcengine:mainfrom
Mijamind719:ov-claude-memory
Feb 22, 2026
Merged

feat(examples): add Claude memory plugin example for OpenViking#246
MaojiaSheng merged 1 commit intovolcengine:mainfrom
Mijamind719:ov-claude-memory

Conversation

@Mijamind719
Copy link
Contributor

@Mijamind719 Mijamind719 commented Feb 22, 2026

  • feat(examples): add a practical Claude memory plugin example

Introduce examples/claude-memory-plugin to show how Claude Code hooks can be wired to OpenViking session APIs for memory lifecycle management.

What this commit mainly does:

  • Adds an end-to-end plugin example (hooks, helper script, plugin manifest, and memory-recall skill)
  • Connects Claude session events to OpenViking session create/ingest/commit flow
  • Provides runnable docs so users can copy the pattern into real projects

Design principles:

  • Keep plugin integration minimal and event-driven, aligned with Claude hook model
  • Support dual-mode operation (local/http) with automatic switching from config
  • Prioritize reliability and reproducibility through a deterministic real-session E2E runner
  • Keep this as an example implementation under examples/, not invasive core changes

Description

Related Issue

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test update

Changes Made

Testing

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have tested this on the following platforms:
    • Linux
    • macOS
    • Windows

Checklist

  • My code follows the project's coding style
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Notes

* feat(examples): add a practical Claude memory plugin example

Introduce `examples/claude-memory-plugin` to show how Claude Code hooks can be wired to OpenViking session APIs for memory lifecycle management.

What this commit mainly does:
- Adds an end-to-end plugin example (hooks, helper script, plugin manifest, and memory-recall skill)
- Connects Claude session events to OpenViking session create/ingest/commit flow
- Provides runnable docs so users can copy the pattern into real projects

Design principles:
- Keep plugin integration minimal and event-driven, aligned with Claude hook model
- Support dual-mode operation (local/http) with automatic switching from config
- Prioritize reliability and reproducibility through a deterministic real-session E2E runner
- Keep this as an example implementation under `examples/`, not invasive core changes
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Mijamind seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@MaojiaSheng MaojiaSheng merged commit 4e0f35e into volcengine:main Feb 22, 2026
3 of 5 checks passed
@github-project-automation github-project-automation bot moved this from Backlog to Done in OpenViking project Feb 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants