feat: add semanticOverride support for SEMANTIC memory strategies by aidandaly24 · Pull Request #696 · aws/agentcore-cli

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 · 2026-03-27T04:32:34Z

Description

Add semanticOverride support for SEMANTIC memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs.

Changes

Schema: Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with Zod validation
Cross-field validation: .refine() rejects semanticOverride on non-SEMANTIC strategy types with a clear error message
Barrel exports: Update primitives/index.ts, agentcore-project.ts for new schema/type exports
LLM-compacted: Update agentcore.ts interface with semanticOverride field

Schema Structure

{
"strategies": [{
"type": "SEMANTIC",
"namespaces": ["/users/{actorId}/facts"],
"semanticOverride": {
"extraction": {
"appendToPrompt": "Extract key facts about the user",
"modelId": "anthropic.claude-3-sonnet-20240229-v1:0"
},
"consolidation": {
"appendToPrompt": "Consolidate user memories",
"modelId": "anthropic.claude-3-haiku-20240307-v1:0"
}
}
}]
}

TUI Screenshots

Validation — pass and fail:

agentcore.json with semanticOverride config:

Synthesized CloudFormation template with SemanticOverride:

All memory unit tests passing (vitest):

Service-Side Note

The CloudFormation resource AWS::BedrockAgentCore::Memory in us-east-1 does not yet include SemanticOverride in its schema. The CLI schema validation and CDK template generation are correct — deployments with overrides will succeed once the service-side schema is updated. Backward compatibility (SEMANTIC without override) is confirmed working.

Related Issue

Closes#678

Documentation PR

N/A — pending service-side schema availability

Type of Change

Bug fix
New feature
Breaking change
Documentation update

Testing

I ran npm run test:unit and npm run test:integ
I ran npm run typecheck
I ran npm run lint
If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Test Coverage

13 new schema unit tests covering:
- Valid extraction-only, consolidation-only, and both overrides
- Rejection of semanticOverride on SUMMARIZATION, USER_PREFERENCE, CUSTOM strategies
- Rejection of empty override (neither extraction nor consolidation)
- appendToPrompt boundary validation (empty, max 30000)
- modelId minimum length validation
- Consolidation-only rejection on USER_PREFERENCE
2 integration tests in agentcore-project.test.ts for full project spec with overrides
E2E deployment testing across 4 scenarios (validate, synth, deploy, invoke)

Checklist

I have read the CONTRIBUTING document
I have added any necessary tests that prove my fix is effective or my feature works
I have updated the documentation accordingly
I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
My changes generate no new warnings
Any dependent changes have been merged and published

Dependent CDK PR: aws/agentcore-l3-cdk-constructs#120 (companion PR with addPropertyOverride implementation)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aidandaly24 · 2026-03-27T04:38:52Z

TUI Screenshots

Screenshots captured during E2E testing of the SemanticOverride feature:

Validation (pass + fail): validate-pass-and-fail.svg
- agentcore validate passes for valid override configs
- agentcore validate fails with clear error for semanticOverride on SUMMARIZATION
Override JSON config: agentcore-json-override-config.svg
- Shows semanticOverride with extraction + consolidation in agentcore.json
CloudFormation template: cfn-template-semantic-override.svg
- Synthesized template with SemanticOverride.Extraction and SemanticOverride.Consolidation
Unit tests: unit-tests-memory-pass.svg
- All 28 memory schema tests passing (vitest)

View all screenshots in the gist

…s#678) Add SemanticOverride schema support to memory strategies, allowing users to customize extraction and consolidation behavior with custom prompts and model IDs on SEMANTIC strategy types. Changes: - Add SemanticExtractionOverrideSchema, SemanticConsolidationOverrideSchema, and SemanticOverrideSchema with at-least-one validation - Add cross-field validation rejecting semanticOverride on non-SEMANTIC types - Export new schemas and types through barrel files - Update LLM-compacted types with semanticOverride interface - Add 13 new unit tests for override validation - Add 2 integration tests for agentcore-project validation Constraint: semanticOverride only valid on SEMANTIC strategy type Constraint: At least one of extraction or consolidation must be provided Rejected: Allow override on all strategy types | CFn only supports it on SEMANTIC Confidence: high Scope-risk: narrow

…gies (#678) (#696)" This reverts commit 5e0f584.

* Revert "feat: add semanticOverride support for SEMANTIC memory strategies (#678) (#696)" This reverts commit 5e0f584. * Revert "feat(memory): add CUSTOM strategy type to agentcore-cli (#677) (#694)" This reverts commit beac707. * fix: restore EPISODIC strategy to configuration.md The revert of the CUSTOM strategy commit inadvertently removed the EPISODIC row from the Memory Strategies table in configuration.md.

Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR aws#694 made -- and aws#713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is aws#241 ("select custom memory strategy, note there is no option to add prompts"); aws#266 removed it as a P0 to stop users picking an unsupported option, aws#694/aws#696 added it back with semanticOverride, and aws#713 reverted both as premature. aws#676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at aws#676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped.

* feat(project): add `project add memory` Registers a `memory` leaf under `project add`, following the same SDK-union -> flat project-schema conversion pattern as `project add harness`. A memory scaffolds no files, so the command only appends an entry to `spec.memories` in agentcore.json; the L3 CDK turns that into an `AWS::BedrockAgentCore::Memory` at deploy time. Flags: --name, --event-expiry-duration, --strategies, --indexed-keys, --stream-delivery-resources, --encryption-key-arn, --execution-role-arn, --tags. --strategies accepts two forms: a comma-separated list of strategy types expanded with the CLI's default namespace templates, or a JSON MemoryStrategyInput[] mirroring the CreateMemory API for strategies that need explicit names, descriptions, or namespaces. clientToken is excluded (it is CreateMemory idempotency and this command makes no API call), and description is excluded until the L3 CDK schema supports it. * feat: add --description to 'project add memory' Stores an optional memory description in agentcore.json, matching the CreateMemory API's description field (max 4096 characters). The generated CDK app pins @aws/agentcore-cdk 0.1.0-alpha.45, whose MemorySchema is a non-strict z.object with no description field, so the key is stripped at synth rather than rejected until aws/agentcore-l3-cdk-constructs#325 ships and that pin is bumped. The flag help text says so. * feat: accept a CUSTOM memory strategy in 'project add memory' The CDK's memory schema already models CUSTOM (@aws/agentcore-cdk 0.1.0-alpha.45 maps it to CFN customMemoryStrategy), so the CLI's four-type enum was the outlier. A customMemoryStrategy in the --strategies JSON now converts to { type: 'CUSTOM', name, description, namespaceTemplates }. The shorthand form still takes managed types only: CUSTOM has no default namespaces to expand. An extraction configuration or memoryRecordSchema is rejected rather than dropped, since the CDK schema carries neither. Also names the offending field in the memory validation error. * revert: drop CUSTOM memory strategy from "project add memory" Reverts 87be86e. I added CUSTOM because the CDK schema already had it in MemoryStrategyTypeSchema, which turns out to be the argument PR #694 made -- and #713 reverted a day later. The CLI has removed CUSTOM twice on purpose. Offering the type without somewhere to put its extraction configuration is #241 ("select custom memory strategy, note there is no option to add prompts"); #266 removed it as a P0 to stop users picking an unsupported option, #694/#696 added it back with semanticOverride, and #713 reverted both as premature. #676 tracks doing it properly. The CDK keeping CUSTOM in its enum without a configuration field is the same hole, not a licence. So both forms are rejected again, now with an error that says why and points at #676. The one thing kept from the reverted commit: memory validation errors name the offending field, since issue.path was being dropped. * refactor: drop the long-form help for --description The one-line flag description is enough; the deploy-time caveat lives in the PR discussion rather than in help output. * docs: comment change * fix: change function name and add comment for clarity * test: add uncovered unsupported stream content type test * style: make json example concrete, remove comments * refactor(project): reuse shared spec validation for memory * fix(project): validate memory JSON inputs * fix(project): harden memory input validation * test(project): colocate memory tests with the add/memory handler Upstream moved the per-resource `project add` tests out of the monolithic project.test.ts into colocated add/<resource>/index.test.ts suites (harness in #2034, online-eval in #2048). Move the memory tests to match, with the same locally-duplicated run/inProject helpers those suites use. project.test.ts is now identical to upstream/refactor again, so this PR no longer touches it. Also drops the DeserializationError, FsReadWriteJson and ReadWriteJson imports, left dead there once the harness tests that used them moved to add/harness/index.test.ts. No test content changed: 187 project tests still pass, now across 10 files instead of 9. * refactor(project): match --strategies JSON to the agentcore.json schema The --strategies flag re-declared its own strategy input schema, modelled on the CreateMemory API's tagged union (semanticMemoryStrategy et al.) and requiring a name. agentcore.json stores strategies flat with an optional name, so the flag accepted a shape the project file never holds and rejected one it does. Parse the JSON form with MemoryStrategySchema itself, wrapped only for the unsupported-field diagnostics, so the flag cannot drift from the schema.

aidandaly24 requested a review from a teamMarch 27, 2026 04:32

github-actionsBot added the size/m PR size: M label Mar 27, 2026

aidandaly24 temporarily deployed to e2e-testing March 27, 2026 04:32 — with GitHub Actions Inactive

aidandaly24 force-pushed the feat/semantic-override-678 branch from a42ba14 to e692ae4Compare March 27, 2026 04:47

aidandaly24 had a problem deploying to e2e-testing March 27, 2026 04:47 — with GitHub Actions Failure

github-actionsBot added size/m PR size: M and removed size/m PR size: M labels Mar 27, 2026

aidandaly24 force-pushed the feat/semantic-override-678 branch from e692ae4 to 911f3e9Compare March 27, 2026 05:20

github-actionsBot removed the size/m PR size: M label Mar 27, 2026

aidandaly24 had a problem deploying to e2e-testing March 27, 2026 05:20 — with GitHub Actions Failure

github-actionsBot added the size/m PR size: M label Mar 27, 2026

jesseturner21 approved these changes Mar 27, 2026
View reviewed changes

aidandaly24 merged commit 5e0f584 into aws:mainMar 27, 2026
16 of 19 checks passed

aidandaly24 added a commit that referenced this pull request Mar 27, 2026
Revert "feat: add semanticOverride support for SEMANTIC memory strate…
7efce7b
…gies (#678) (#696)" This reverts commit 5e0f584.

aidandaly24 mentioned this pull request Mar 27, 2026
revert: remove CUSTOM strategy and semanticOverride support #713
Merged
11 tasks

aidandaly24 added a commit that referenced this pull request Mar 27, 2026
Revert "feat: add semanticOverride support for SEMANTIC memory strate…
8a8c297
…gies (#678) (#696)" This reverts commit 5e0f584.

notgitika mentioned this pull request Aug 18, 2026
feat(project): add project add memory#2025
Merged