feat(project): scaffold add harness handler by Hweinstock · Pull Request #1998 · aws/agentcore-cli

Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock · 2026-08-13T19:16:48Z

Problem

We're missing functionality to add resources to a project. This PR sets up the handler for agentcore project add harness as an example, and scaffolds the remaining work for add.

Solution

setup a handler that takes the same flags at the imperative harness create (with a extra few project specific ones). Alternatively considered using different flags from imperative, but this creates an inconsistent UX where project command inputs are similar to api shapes, but slightly different (ex. containerUri is top level, vs nested in json).
convert those flags into the spec format expected by the schemas.
scaffold an add function for the shared functionality.

Testing / Verification

created a project, attempted to add a harness and got the not implemented error.
add unit tests for the flag parsing.

Next Steps

I want to move the scaffolding of runtime into the add function, then call that from the handler when we're scaffolding. This will make it easier to re-use the logic, and handle harness in the same place.
implement the rest of add via json source.

codecov-commenter · 2026-08-13T19:19:36Z

Codecov Report

❌ Patch coverage is 99.50860% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (9398c03) to head (d9138cd).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/handlers/project/add/harness/index.ts	99.48%	2 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #1998 +/- ##
============================================
+ Coverage 96.91% 96.96% +0.04% 
============================================
Files 356 357 +1 Lines 20136 20531 +395 ============================================
+ Hits 19515 19908 +393 - Misses 621 623 +2

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Hweinstock · 2026-08-13T19:18:23Z

 }

+ // eslint-disable-next-line require-yield
+ public async *add<TResource extends ProjectResource>(


i'm imagining minimal special casing here. We'll want to scaffold files for runtime/harness, then the rest should be simple shared logic to write the schema changes. We will also need some special casing for harness since it links to the config in the scaffolded files.

Hweinstock · 2026-08-13T19:19:39Z

+ });
+
+/** Converts the SDK's tagged-union model config into the flat project-schema shape. */
+function toModelConfig(modelConfig: HarnessModelConfiguration): HarnessModel {


we handle all the api shape --> project schema conversion in the handler to keep the shared logic clean.

jariy17 · 2026-08-14T15:57:20Z

+ ])("%s", async (_label, flags) => {
+ await inProject();
+ // TODO: update to verify that the project updates.
+ await expect(run(["add", "harness", ...flags])).rejects.toThrow("not yet implemented");


TODO: MAke sure you fix tests after implementation

notgitika · 2026-08-14T17:26:32Z

 }

+ // eslint-disable-next-line require-yield
+ public async *addResource<TResource extends ProjectResource>(


notgitika · 2026-08-14T17:35:15Z

+ if ("agentCoreGateway" in c && c.agentCoreGateway) {
+ return {
+ type: tool.type,
+ name: tool.name,
+ config: {
+ agentCoreGateway: {
+ gatewayArn: requireField(c.agentCoreGateway.gatewayArn, "agentCoreGateway.gatewayArn"),
+ },
+ },
+ };


what about when users set outbound auth or JWT here? are these being dropped or are they somewhere where I'm missing them. I am looking at toAuthorizationConfig below and I see those fields.

good catch, looks like we want to wire up the field here
agentcore-cli/src/projectSchemas/harness.ts
Line 195 in a9d34be
outboundAuth: HarnessGatewayOutboundAuthSchema.optional(),
from https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_HarnessAgentCoreGatewayConfig.html. I'll track this as a follow-up.

notgitika · 2026-08-14T17:38:47Z

+ async function inBuildableProject(): Promise<string> {
+ const projectRoot = await inProject("MyAgent");


Hweinstock added 3 commits August 13, 2026 18:45

feat(project): implement add harness scaffolding
7dc2d57

chore: merge in refactor branch
b575a30

refactor(test): clean up tests
bb093ca

Hweinstock changed the title ~~Feat/add harness~~feat(project): scaffold add harness handlerAug 13, 2026

github-actionsBot added the agentcore-harness-reviewing AgentCore Harness review in progress label Aug 13, 2026

github-actionsBot removed the agentcore-harness-reviewing AgentCore Harness review in progress label Aug 13, 2026

refactor(project): rename add to addResource
d9138cd

Hweinstock force-pushed the feat/add-harness branch from 2734b07 to d9138cdCompare August 13, 2026 19:51

Hweinstock commented Aug 13, 2026
View reviewed changes

Hweinstock marked this pull request as ready for review August 13, 2026 19:54

jariy17 approved these changes Aug 14, 2026
View reviewed changes

Hweinstock requested a review from notgitika August 14, 2026 17:16

tejaskash approved these changes Aug 14, 2026
View reviewed changes

notgitika approved these changes Aug 14, 2026
View reviewed changes

Hweinstock merged commit 64d601f into aws:refactorAug 14, 2026
8 of 16 checks passed

Hweinstock deleted the feat/add-harness branch August 14, 2026 19:31

Hweinstock mentioned this pull request Aug 14, 2026
feat(project): implement add functionality. #2004
Merged

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

jariy17 mentioned this pull request Aug 28, 2026
feat(project): add project add evaluator code-based#2144
Open