Add MemPalace as a shared MCP workflow#26102
Conversation
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/ec374765-400d-4135-889f-9bd4a6254c43 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/ec374765-400d-4135-889f-9bd4a6254c43 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
@copilot use mempalace in a daily agentic workflow (pick a good candidate, update prompt) |
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/b5ef527a-4579-4126-81cb-3c04ba3d16b7 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/b5ef527a-4579-4126-81cb-3c04ba3d16b7 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Updated Why What changed in the prompt:
The palace is backed by Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
There was a problem hiding this comment.
Pull request overview
Adds a reusable MemPalace MCP configuration intended to provide persistent, semantic “memory” across workflow runs, and wires it into the daily-fact workflow to avoid repeating previously-posted topics.
Changes:
- Introduces a new shared MCP import (
shared/mcp/mempalace.md) meant to configure and install MemPalace + enablecache-memory. - Updates
daily-fact.mdto query MemPalace before selecting a topic and record the chosen topic after posting. - Regenerates
daily-fact.lock.ymlto include MemPalace MCP server configuration, Python setup, and cache-memory persistence jobs/steps.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/shared/mcp/mempalace.md | Adds a shared MCP server definition for MemPalace and enables cache-memory persistence. |
| .github/workflows/daily-fact.md | Adds “load memory” and “save memory” instructions and imports the MemPalace shared config. |
| .github/workflows/daily-fact.lock.yml | Lockfile regen reflecting the new import, MemPalace MCP server wiring, Python setup, and cache-memory persistence. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comments suppressed due to low confidence (2)
.github/workflows/shared/mcp/mempalace.md:50
- The
pip install "mempalace==3.2.0"step runs in the workflow runner environment, but MCP stdio servers are executed in isolated containers via the gateway. This means the MemPalace package installed here won’t be available to the server process unless the server is also run in that same environment. Consider moving the installation into the MCP server container setup (e.g., using a purpose-built image or an entrypoint that installs dependencies) so the gateway-launched server can actually importmempalace.
steps:
- name: Install MemPalace
run: pip install "mempalace==3.2.0"
.github/workflows/daily-fact.lock.yml:773
- The gateway JSON config for
mempalaceincludes"type": "stdio"with a raw"command": "python". Per the MCP Gateway spec, stdio servers must be containerized andcommandis not supported; the gateway is likely to reject this config or fail to start the server. Update the underlying shared MCP config so this expands to a containerized server (container+entrypoint/entrypointArgs) instead ofcommand.
"type": "stdio",
"command": "python",
"args": [
- Files reviewed: 3/3 changed files
- Comments generated: 2
| mempalace: | ||
| type: stdio | ||
| command: "python" | ||
| args: | ||
| - "-m" | ||
| - "mempalace.mcp_server" | ||
| - "--palace" | ||
| - "/tmp/gh-aw/cache-memory/palace" |
| [mcp_servers.mempalace] | ||
|
|
Adds MemPalace — a local ChromaDB-backed semantic memory system — as a shared MCP workflow importable by any agentic workflow.
Changes
shared/mcp/mempalace.md— new shared workflow that:mempalace==3.2.0via pip in a pre-stepstdioMCP server (python -m mempalace.mcp_server) with the palace rooted at/tmp/gh-aw/cache-memory/palacecache-memory: trueso the ChromaDB palace persists across runs (palace is auto-created on first use)daily-fact.md— updated to use MemPalace for variety enforcement across daily runs:mempalace_search(wing:daily-facts) before selecting a topic, so previously celebrated PRs, issues, releases, and contributors are excludedmempalace_add_drawerafter posting, storing the cited identifier into one of five canonical rooms (pr,release,issue,contributor,pattern)Usage
Override cache retention (default 7 days, max 90):