Integrate Long-Term Memory with Qoder via Hooks

Prerequisites

• Qoder IDE or Qoder CLI is installed and functional.

• Python >= 3.10.

• Obtained theAnalyticDB for PostgreSQLLong-Term Memory service API URL and token.

• Obtained theadbpgmem_mcp_selfhosted project source codeadbpgmem-mcp-server-0.2.0.tar.gz.

  Extract the archive to a directory named adbpgmem_mcp_selfhosted. All paths in the following steps refer to this extracted directory.

Installation

Install the Python package viapip install to register the Hook CLI entry points:

pip install -e /path/to/adbpgmem_mcp_selfhosted

After installation, the following Qoder-specific CLI commands will be available:

Verify installation:

which adbpgmem-qoder-stop
# Should output the installation path, e.g., /usr/local/bin/adbpgmem-qoder-stop

Parameters

Method 1: Environment Variables

Export environment variables before starting Qoder. Hooks inherit environment variables from the parent process:

export ADBPGMEM_API_URL="https://api-longmemory-cn-chengdu.opentrust.net"
export ADBPGMEM_API_TOKEN="sk-your-token-here"
export ADBPGMEM_USER_ID="your.username"

Method 2: Configuration File (Recommended)

Once written, no further action is needed. ADBPGMEM_USER_ID can be omitted (defaults to the system username).

Global configuration (recommended, applies to all projects):

mkdir -p ~/.qoder
cat > ~/.qoder/adbpgmem.conf << 'EOF'
ADBPGMEM_API_URL="https://api-longmemory-cn-chengdu.opentrust.net"
ADBPGMEM_API_TOKEN="sk-your-token-here"
ADBPGMEM_USER_ID="your.username"
EOF

Project-level configuration (applies to the current project only):

mkdir -p .qoder
cat > .qoder/adbpgmem.conf << 'EOF'
ADBPGMEM_API_URL="https://api-longmemory-cn-chengdu.opentrust.net"
ADBPGMEM_API_TOKEN="sk-your-token-here"
ADBPGMEM_USER_ID="your.username"
EOF

Global Registration (Recommended)

Writes to ~/.qoder/settings.json, applying to all projects:

#  (Optional) Back up existing configuration
cp ~/.qoder/settings.json ~/.qoder/settings.json.bak 2>/dev/null

# Global registration (auto-detect platform)
adbpgmem-install-hooks --global

#  Or manually specify Qoder platform
adbpgmem-install-hooks --platform qoder --global

Project-Level Registration

Writes to <project>/.qoder/settings.json, applying only to the current project:

#  (Optional) Back up existing configuration
cp .qoder/settings.json .qoder/settings.json.bak 2>/dev/null

# Project-level registration
adbpgmem-install-hooks
#  Or manually specify
adbpgmem-install-hooks --platform qoder

Selective Registration by Type

The installer supports selective registration by Hook responsibility group:

# Install only write-type Hooks (stop + pretooluse)
adbpgmem-install-hooks --global --type write

# Install only read-type Hooks (userpromptsubmit)
adbpgmem-install-hooks --global --type read

# Install all (default)
adbpgmem-install-hooks --global --type all

After registration, settings.json contains the following Hook configuration:

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "matcher": "",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-userpromptsubmit", "timeout": 10}
        ]
      }
    ],
    "Stop": [
      {
        "matcher": "",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-stop", "timeout": 30}
        ]
      }
    ],
    "PreToolUse": [
      {
        "matcher": "*",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-pretooluse", "timeout": 2}
        ]
      }
    ]
  }
}

Uninstall Hooks

# Auto-detect platform (recommended)
adbpgmem-uninstall-hooks --global   # Global uninstall
adbpgmem-uninstall-hooks            # Project-level uninstall

# Manually specify platform
adbpgmem-uninstall-hooks --platform qoder --global

# Also clean up session injection marker directory
adbpgmem-uninstall-hooks --global --remove-sessions

Verify Registration

# Check if Hooks are registered successfully
cat ~/.qoder/settings.json
# Should contain entries like adbpgmem-qoder-stop

Functional test: Send a message in Qoder and check whether the AI response includes historical memory context.

View Logs

Hook runtime logs are written to ~/.qoder/adbpgmem-hooks.log. View the latest logs for troubleshooting:

tail -50 ~/.qoder/adbpgmem-hooks.log

Invocation

Hooks run fully automatically without any manual operation. Qoder automatically triggers at the following events:

Detailed Hook Behavior

# adbpgmem cross-session memory

1. Project uses Go 1.22 + Gin framework, ORM uses GORM v2
2. Database: PostgreSQL 15, connection pool: PgBouncer, max connections: 50
3. APIs uniformly use RESTful style, error codes follow RFC 7807

Scenario 1: Automatically Inherit Historical Decisions in New Sessions

You have determined the tech stack for a project and want Qoder AI to automatically know it when starting a new session.

Session 1 (memory saved via MCP tools or other methods):

You: Remember: the project uses Python 3.11 + FastAPI, database PostgreSQL 15, cache Redis 7

Session 2 (new session started days later):

You: Help me add a new API endpoint

← adbpgmem-qoder-userpromptsubmit triggered automatically (first prompt)
← Dual-query searches user prompt and "project_name project architecture tech stack"
← Injects matched memories into additionalContext
← Creates session marker file, subsequent messages no longer trigger

Qoder AI: Based on the project's FastAPI + PostgreSQL 15 tech stack, I'll create the new endpoint...
         [Automatically uses the correct framework and database version]

No need to manually inform Qoder AI about the tech stack. Historical memories are automatically injected with the first message.

Scenario 2: Prevent Memory from Scattering to Local Files

Qoder AI attempts to write memories to the local MEMORY.md file during a conversation.

Qoder AI: [Attempts to call the Write tool to write to MEMORY.md]
          "Let me record this architectural decision in MEMORY.md..."

← adbpgmem-qoder-pretooluse triggered automatically
← Detected target path matches "MEMORY.md" guard pattern
← Returns decision: "block" + permissionDecision: "deny"
← reason: "Memories should be stored in adbpgmem via the add_memory MCP tool"

Qoder AI: [Received block signal, switches to using add_memory MCP tool]
          Architectural decision saved to the adbpgmem memory store.

All memories are centrally stored in adbpgmem, avoiding scattering across local files that would prevent cross-session retrieval.

Scenario 3: Combined MCP + Hooks (Most Complete Solution)

Combine MCP tools and Hooks for the most complete memory capability.

Configuration Steps:

# 1. Install the Python package (required for Hooks)
pip install -e /path/to/adbpgmem_mcp_selfhosted

# 2. Register MCP Server (edit ~/.qoder/settings.json, add mcpServers configuration)

# 3. Register Hooks
adbpgmem-install-hooks --platform qoder --global

# 4. Configure AGENTS.md (guide Qoder AI to proactively use MCP tools)
cat >> AGENTS.md << 'EOF'

# MCP Servers
- **adbpgmem**: Persistent memory service. At the start of each session, use search_memories
  to search for relevant context. Use add_memory to save architectural decisions,
  debugging experience, and coding patterns. Better to save too much than to miss something.
EOF

Complete ~/.qoder/settings.json example (MCP + Hooks coexistence):

{
  "mcpServers": {
    "adbpgmem": {
      "command": "uvx",
      "args": ["--from", "/path/to/adbpgmem_mcp_selfhosted", "adbpgmem-mcp-server"],
      "env": {
        "ADBPGMEM_API_URL": "https://api-longmemory-cn-chengdu.opentrust.net",
        "ADBPGMEM_API_TOKEN": "sk-your-token-here",
        "ADBPGMEM_USER_ID": "your.username"
      }
    }
  },
  "hooks": {
    "UserPromptSubmit": [
      {
        "matcher": "",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-userpromptsubmit", "timeout": 10}
        ]
      }
    ],
    "Stop": [
      {
        "matcher": "",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-stop", "timeout": 30}
        ]
      }
    ],
    "PreToolUse": [
      {
        "matcher": "*",
        "hooks": [
          {"type": "command", "command": "adbpgmem-qoder-pretooluse", "timeout": 2}
        ]
      }
    ]
  }
}

Combined Usage Benefits: