feat(agents): Agent Designer Phase 1 — AGENTS_API_ENABLED flag plumbing + docs#593
Merged
Merged
Conversation
Phase 1 (PR-4). Completes Phase 1 deployability: the /agents surface can now
be turned on per environment. No new AWS resources — the flag only gates
whether the routes 404 (the assistant store it reads is always present).
- config.ts: AgentsConfig { enabled }; CDK_AGENTS_API_ENABLED (default off,
empty-string-safe) or an `agents.enabled` cdk.json context, mirroring
memorySpaces exactly
- app-api-environment.ts: AGENTS_API_ENABLED env on app-api
- infra tests: default-off / opt-on assertion; mock-config default
- docs: agent-designer.md Phase-1 status (+ the two refinements and the
Oliver-dogfood-gated-on-Phase-3 note); CHANGELOG [Unreleased]
The live Oliver dogfood (D6) is deliberately NOT included: it needs Phase 3
harness resolution + Memory Spaces deployed to the target env before a
memory_space binding resolves at invocation. Tracked as the Phase 3 payoff.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent Designer — Phase 1, PR-4 (deployability + docs)
Builds on #591 + #592. Completes Phase 1 by making the
/agentssurface turn-on-able per environment, and documents Phase-1 status. No application-logic change; no new AWS resources.What's here
AgentsConfig { enabled }, driven byCDK_AGENTS_API_ENABLED(default off, empty-string-safe) or anagents.enabledcdk.json context, mirroringmemorySpacesexactly. SetsAGENTS_API_ENABLEDon app-api. The flag only gates whether the/agents/*routes 404 — the assistant store they read is always present, so no table/bucket wiring is needed.app-api-environment.test.ts;mock-configdefault.agent-designer.mdPhase-1 status (marks P0/P1 done, records the two refinements: KB synth-on-read/reject-on-write, andmodelConfigoptional-in-storage);CHANGELOG.md[Unreleased].Deliberately NOT here — the live Oliver dogfood
D6's payoff (Oliver reads his bound Memory Space) is gated on two things not yet in place: Phase 3 harness resolution (nothing consumes a
memory_spacebinding at invocation yet) and Memory Spaces deployed to the target environment (per the memory-spaces app-api wiring note). Shipping a seeded Oliver now would store a binding that can't resolve. It's the headline Phase-3 deliverable instead.Testing
npx tsc --noEmitclean; 67 infra tests pass (incl. the newAGENTS_API_ENABLEDgate).Next
Phase 2 (bindable-primitives catalog — the RBAC palette) or Phase 3 (harness resolution — the memory dogfood payoff). Recommend Phase 3 to cash in D6.
🤖 Generated with Claude Code