Merge branch 'main' into rename-agents-to-runtimes

Author: jesseturner21

.github/workflows/release.yml

@@ -108,6 +108,12 @@ jobs:
           echo "branch=release/v$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "New version: $NEW_VERSION"
 
+      - name: Regenerate JSON schema
+        run: |
+          npm run build
+          node scripts/generate-schema.mjs
+          echo "✓ JSON schema regenerated"
+
       - name: Create release branch and PR
         env:
           NEW_VERSION: ${{ steps.bump.outputs.version }}

docs/commands.md

@@ -225,12 +225,12 @@ agentcore add memory \
   --expiry 30
 ```
 
-| Flag                   | Description                                                                           |
-| ---------------------- | ------------------------------------------------------------------------------------- |
-| `--name <name>`        | Memory name                                                                           |
-| `--strategies <types>` | Comma-separated: `SEMANTIC`, `SUMMARIZATION`, `USER_PREFERENCE`, `EPISODIC`, `CUSTOM` |
-| `--expiry <days>`      | Event expiry duration in days (default: 30, min: 7, max: 365)                         |
-| `--json`               | JSON output                                                                           |
+| Flag                   | Description                                                                 |
+| ---------------------- | --------------------------------------------------------------------------- |
+| `--name <name>`        | Memory name                                                                 |
+| `--strategies <types>` | Comma-separated: `SEMANTIC`, `SUMMARIZATION`, `USER_PREFERENCE`, `EPISODIC` |
+| `--expiry <days>`      | Event expiry duration in days (default: 30, min: 7, max: 365)               |
+| `--json`               | JSON output                                                                 |
 
 ### add gateway
 
@@ -474,22 +474,23 @@ Start local development server with hot-reload.
 agentcore dev
 agentcore dev --agent MyAgent --port 3000
 agentcore dev --logs                      # Non-interactive
-agentcore dev --invoke "Hello" --stream   # Direct invoke
+agentcore dev "Hello" --stream            # Invoke running dev server
+agentcore dev "Hello" --agent MyAgent     # Invoke specific agent
 
 # MCP protocol dev commands
-agentcore dev --invoke list-tools
-agentcore dev --invoke call-tool --tool myTool --input '{"arg": "value"}'
+agentcore dev list-tools
+agentcore dev call-tool --tool myTool --input '{"arg": "value"}'
 ```
 
-| Flag                    | Description                                            |
-| ----------------------- | ------------------------------------------------------ |
-| `-p, --port <port>`     | Port (default: 8080; MCP uses 8000, A2A uses 9000)     |
-| `-a, --agent <name>`    | Agent to run (required if multiple agents)             |
-| `-i, --invoke <prompt>` | Invoke running server                                  |
-| `-s, --stream`          | Stream response (with --invoke)                        |
-| `-l, --logs`            | Non-interactive stdout logging                         |
-| `--tool <name>`         | MCP tool name (with `--invoke call-tool`)              |
-| `--input <json>`        | MCP tool arguments as JSON (with `--invoke call-tool`) |
+| Flag / Argument      | Description                                          |
+| -------------------- | ---------------------------------------------------- |
+| `[prompt]`           | Send a prompt to a running dev server                |
+| `-p, --port <port>`  | Port (default: 8080; MCP uses 8000, A2A uses 9000)   |
+| `-a, --agent <name>` | Agent to run or invoke (required if multiple agents) |
+| `-s, --stream`       | Stream response when invoking                        |
+| `-l, --logs`         | Non-interactive stdout logging                       |
+| `--tool <name>`      | MCP tool name (with `call-tool` prompt)              |
+| `--input <json>`     | MCP tool arguments as JSON (with `--tool`)           |
 
 ### invoke
 

docs/configuration.md

@@ -239,13 +239,12 @@ on the next deployment.
 
 ### Memory Strategies
 
-| Strategy          | Description                                                 |
-| ----------------- | ----------------------------------------------------------- |
-| `SEMANTIC`        | Vector-based similarity search for relevant context         |
-| `SUMMARIZATION`   | Compressed conversation history                             |
-| `USER_PREFERENCE` | Store user-specific preferences and settings                |
-| `EPISODIC`        | Capture and reflect on meaningful interaction episodes      |
-| `CUSTOM`          | Self-managed strategy with user-controlled extraction logic |
+| Strategy          | Description                                            |
+| ----------------- | ------------------------------------------------------ |
+| `SEMANTIC`        | Vector-based similarity search for relevant context    |
+| `SUMMARIZATION`   | Compressed conversation history                        |
+| `USER_PREFERENCE` | Store user-specific preferences and settings           |
+| `EPISODIC`        | Capture and reflect on meaningful interaction episodes |
 
 Strategy configuration:
 

docs/local-development.md

@@ -20,20 +20,16 @@ agentcore dev --logs
 
 ## Invoking Local Agents
 
-With the dev server running, open another terminal:
+Start the dev server in one terminal, then send prompts from another:
 
 ```bash
-# Interactive chat
-agentcore invoke
-
-# Single prompt
-agentcore invoke "What can you do?"
-
-# With streaming
-agentcore invoke "Tell me a story" --stream
+# Terminal 1: start the dev server
+agentcore dev --logs
 
-# Direct invoke to running server
-agentcore dev --invoke "Hello" --stream
+# Terminal 2: send prompts
+agentcore dev "What can you do?"
+agentcore dev "Tell me a story" --stream
+agentcore dev "Hello" --agent MyAgent
 ```
 
 ## Environment Setup

docs/memory.md

@@ -168,13 +168,12 @@ conversations, enabling cross-session recall via semantic search.
 
 ## Memory Strategies
 
-| Strategy          | Description                                                 |
-| ----------------- | ----------------------------------------------------------- |
-| `SEMANTIC`        | Vector-based similarity search for relevant context         |
-| `SUMMARIZATION`   | Compressed conversation history                             |
-| `USER_PREFERENCE` | Store user-specific preferences and settings                |
-| `EPISODIC`        | Capture and reflect on meaningful interaction episodes      |
-| `CUSTOM`          | Self-managed strategy with user-controlled extraction logic |
+| Strategy          | Description                                            |
+| ----------------- | ------------------------------------------------------ |
+| `SEMANTIC`        | Vector-based similarity search for relevant context    |
+| `SUMMARIZATION`   | Compressed conversation history                        |
+| `USER_PREFERENCE` | Store user-specific preferences and settings           |
+| `EPISODIC`        | Capture and reflect on meaningful interaction episodes |
 
 You can combine multiple strategies:
 
@@ -189,36 +188,6 @@ You can combine multiple strategies:
 }
 ```
 
-### Self-Managed (Custom) Strategy
-
-The `CUSTOM` strategy lets you control memory extraction logic externally rather than relying on built-in
-implementations. This is useful when you need specialized extraction pipelines or want to integrate with your own
-processing infrastructure.
-
-**Prerequisites:** CUSTOM strategies require user-managed extraction logic and are not functional without it. You must
-implement your own extraction mechanism (e.g., via AWS Lambda).
-
-**Key characteristics:**
-
-- No default namespaces are assigned — you provide your own or omit them
-- Each memory supports at most one CUSTOM strategy
-- You are responsible for implementing the extraction logic that processes memory events
-
-```json
-{
-  "type": "AgentCoreMemory",
-  "name": "MyMemory",
-  "eventExpiryDuration": 30,
-  "strategies": [
-    {
-      "type": "CUSTOM",
-      "name": "my_custom_strategy",
-      "description": "Custom extraction logic"
-    }
-  ]
-}
-```
-
 ### Strategy Options
 
 Each strategy can have optional configuration:

src/assets/__tests__/__snapshots__/assets.snapshot.test.ts.snap

@@ -1696,11 +1696,6 @@ def get_memory_session_manager(session_id: str, actor_id: str) -> Optional[Agent
 {{/if}}
 {{#if (includes memoryProviders.[0].strategies "SUMMARIZATION")}}
         f"/summaries/{actor_id}/{session_id}": RetrievalConfig(top_k=3, relevance_score=0.5),
-{{/if}}
-{{#if (includes memoryProviders.[0].strategies "CUSTOM")}}
-        # TODO: Add your custom namespace and retrieval config.
-        # Custom strategies use user-controlled extraction logic.
-        # Example: f"/custom/{actor_id}/data": RetrievalConfig(top_k=3, relevance_score=0.5),
 {{/if}}
     }
 {{/if}}
@@ -3662,11 +3657,6 @@ def get_memory_session_manager(session_id: str, actor_id: str) -> Optional[Agent
 {{/if}}
 {{#if (includes memoryProviders.[0].strategies "SUMMARIZATION")}}
         f"/summaries/{actor_id}/{session_id}": RetrievalConfig(top_k=3, relevance_score=0.5),
-{{/if}}
-{{#if (includes memoryProviders.[0].strategies "CUSTOM")}}
-        # TODO: Add your custom namespace and retrieval config.
-        # Custom strategies use user-controlled extraction logic.
-        # Example: f"/custom/{actor_id}/data": RetrievalConfig(top_k=3, relevance_score=0.5),
 {{/if}}
     }
 {{/if}}
@@ -4010,7 +4000,7 @@ file maps to a JSON config file and includes validation constraints as comments.
 - **BuildType**: \`'CodeZip'\` | \`'Container'\`
 - **NetworkMode**: \`'PUBLIC'\`
 - **RuntimeVersion**: \`'PYTHON_3_10'\` | \`'PYTHON_3_11'\` | \`'PYTHON_3_12'\` | \`'PYTHON_3_13'\`
-- **MemoryStrategyType**: \`'SEMANTIC'\` | \`'SUMMARIZATION'\` | \`'USER_PREFERENCE'\` | \`'EPISODIC'\` | \`'CUSTOM'\`
+- **MemoryStrategyType**: \`'SEMANTIC'\` | \`'SUMMARIZATION'\` | \`'USER_PREFERENCE'\` | \`'EPISODIC'\`
 
 ### Build Types
 

src/assets/agents/AGENTS.md

@@ -63,7 +63,7 @@ file maps to a JSON config file and includes validation constraints as comments.
 - **BuildType**: `'CodeZip'` | `'Container'`
 - **NetworkMode**: `'PUBLIC'`
 - **RuntimeVersion**: `'PYTHON_3_10'` | `'PYTHON_3_11'` | `'PYTHON_3_12'` | `'PYTHON_3_13'`
-- **MemoryStrategyType**: `'SEMANTIC'` | `'SUMMARIZATION'` | `'USER_PREFERENCE'` | `'EPISODIC'` | `'CUSTOM'`
+- **MemoryStrategyType**: `'SEMANTIC'` | `'SUMMARIZATION'` | `'USER_PREFERENCE'` | `'EPISODIC'`
 
 ### Build Types
 

src/assets/python/a2a/strands/capabilities/memory/session.py

@@ -21,11 +21,6 @@ def get_memory_session_manager(session_id: str, actor_id: str) -> Optional[Agent
 {{/if}}
 {{#if (includes memoryProviders.[0].strategies "SUMMARIZATION")}}
         f"/summaries/{actor_id}/{session_id}": RetrievalConfig(top_k=3, relevance_score=0.5),
-{{/if}}
-{{#if (includes memoryProviders.[0].strategies "CUSTOM")}}
-        # TODO: Add your custom namespace and retrieval config.
-        # Custom strategies use user-controlled extraction logic.
-        # Example: f"/custom/{actor_id}/data": RetrievalConfig(top_k=3, relevance_score=0.5),
 {{/if}}
     }
 {{/if}}

src/assets/python/http/strands/capabilities/memory/session.py

@@ -21,11 +21,6 @@ def get_memory_session_manager(session_id: str, actor_id: str) -> Optional[Agent
 {{/if}}
 {{#if (includes memoryProviders.[0].strategies "SUMMARIZATION")}}
         f"/summaries/{actor_id}/{session_id}": RetrievalConfig(top_k=3, relevance_score=0.5),
-{{/if}}
-{{#if (includes memoryProviders.[0].strategies "CUSTOM")}}
-        # TODO: Add your custom namespace and retrieval config.
-        # Custom strategies use user-controlled extraction logic.
-        # Example: f"/custom/{actor_id}/data": RetrievalConfig(top_k=3, relevance_score=0.5),
 {{/if}}
     }
 {{/if}}

src/cli/commands/add/__tests__/add-memory.test.ts

@@ -51,17 +51,16 @@ describe('add memory command', () => {
       expect(json.error.includes('INVALID'), `Error: ${json.error}`).toBeTruthy();
     });
 
-    // Issue #677: CUSTOM strategy is now supported
-    it('creates memory with CUSTOM strategy', async () => {
-      const memoryName = `memCustom${Date.now()}`;
+    // Issue #235: CUSTOM strategy has been removed
+    it('rejects CUSTOM strategy', async () => {
       const result = await runCLI(
-        ['add', 'memory', '--name', memoryName, '--strategies', 'CUSTOM', '--json'],
+        ['add', 'memory', '--name', 'testCustom', '--strategies', 'CUSTOM', '--json'],
         projectDir
       );
-      expect(result.exitCode, `stdout: ${result.stdout}, stderr: ${result.stderr}`).toBe(0);
+      expect(result.exitCode).toBe(1);
       const json = JSON.parse(result.stdout);
-      expect(json.success).toBe(true);
-      expect(json.memoryName).toBe(memoryName);
+      expect(json.success).toBe(false);
+      expect(json.error.includes('CUSTOM'), `Error: ${json.error}`).toBeTruthy();
     });
   });