Skip to content

feat: add Memcode memory plugin - #58

Closed
vivekgupta-memcode wants to merge 2 commits into
vastsa:mainfrom
vivekgupta-memcode:feat/memcode
Closed

vivekgupta-memcode wants to merge 2 commits into
vastsa:mainfrom
vivekgupta-memcode:feat/memcode

Conversation

@vivekgupta-memcode

@vivekgupta-memcode vivekgupta-memcode commented Sep 20, 2026 •

Copy link
Copy Markdown

Summary

  • add an official-style in.memcode.memory plugin with test-connection, save, search, and retrieve tools
  • keep outbound access on a fixed Memcode allowlist and read credentials only from the plugin environment
  • mark memory writes high risk and ship the built .piplug package plus catalog entry

The plugin does not accept raw credentials as tool inputs and does not log them.

@vercel

vercel Bot commented Sep 20, 2026

Copy link
Copy Markdown

@vivekgupta-memcode is attempting to deploy a commit to the vastsa's projects Team on Vercel.

A member of the Team first needs to authorize it.

@vastsa

vastsa commented Sep 20, 2026

Copy link
Copy Markdown
Owner

感谢贡献,现在插件可以直接在平台提交,自动审核,谢谢:https://plugins.aiuo.net/

@vivekgupta-memcode

Copy link
Copy Markdown
Author

@vastsa
我已经直接发布了这个插件,如果你能在你的落地页上添加关于记忆集成的介绍,我会非常乐意,或者我们也可以就此写一篇博客什么的

@vastsa

vastsa commented Sep 21, 2026

Copy link
Copy Markdown
Owner

@vastsa 我已经直接发布了这个插件,如果你能在你的落地页上添加关于记忆集成的介绍,我会非常乐意,或者我们也可以就此写一篇博客什么的

您好,可以的,如果有介绍我们可以贴上去,非常感谢

@vastsa

vastsa commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Closing this as part of the migration that removed plugin sources from this repository.

Since commit 38284f1 the plugins/ tree is gone: this repository only ships the published catalog.json and the packages/*.piplug artifacts. Sources now live in each author's own repository, and every release goes through the plugin center, which packs the files, audits the source, records the SHA-256 and publishes the version.

Your work is not lost — your branch and fork stay exactly as they are. To ship in.memcode.memory:

  1. move plugins/in.memcode.memory/ into your own public repository (e.g. vivekgupta-memcode/pi-desktop-memcode), keeping manifest.json at the package root;
  2. tag the version you want reviewed (v<x.y.z>); the tag, or a commit SHA, becomes the sourceRef the review reads;
  3. sign in at https://plugins.aiuo.net → My Plugins → Create plugin: upload the package, bind that repository, submit — or let an agent run the publishing skill https://plugins.aiuo.net/skill.md over MCP https://plugins.aiuo.net/mcp;
  4. later versions are submitted from the plugin's own page.

One detail worth keeping: the center rebuilds the published manifest from what you submit, so send ui, contributes, activationEvents, fs and net in full — anything omitted is dropped and the installed plugin becomes invalid.

This repository still welcomes distribution-side contributions (a broken .piplug, a stale catalog entry, website or docs fixes); anything that adds plugins/<id>/ will be closed with this pointer. Thanks for the work on in.memcode.memory — the review gate is the same, it just runs against your own repository now.

@vastsa vastsa closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants