Repository navigation
Open
5 / 165 of 16 issues completedOpen
5 / 165 of 16 issues completed
Copy link
Labels
enhancementNew feature or requestNew feature or requestneeds-triageIssue needs triageIssue needs triageprojectThe issues with an ongoing projectThe issues with an ongoing project
Description
Add agentcore_session: run several jobs in one Amazon Bedrock AgentCore Runtime session from a durable function. It builds on agentcore(), which runs one job per session.
API
agentcore_session creates one session, runs a handler that sends jobs with session.invoke, and stops the session when the handler ends. Jobs share the session's files and memory.
Rules for developers (documented, not enforced)
- The runtime idle timeout must be longer than any wait between jobs. Otherwise AgentCore gives the session ID a new microVM, and the session state is lost.
- The session
timeoutmust fit the runtime'smaxLifetime. - Parallel
invokecalls on one session are the developer's responsibility.
Plan
Each item is one small pull request. Items without a dependency can run in parallel.
- [AgentCore session] E1: Move the session-ID and stop steps of agentcore() into helpers #939 E1
- [AgentCore session] E2: Move the job steps of agentcore() into a helper #940 E2 (after [AgentCore session] E1: Move the session-ID and stop steps of agentcore() into helpers #939)
- [AgentCore session] E3: Add the agentcore_session types #941 E3
- [AgentCore session] E4: Validate the agentcore_session config #942 E4 (after [AgentCore session] E3: Add the agentcore_session types #941)
- [AgentCore session] E5: Add agentcore_session with the session lifecycle #943 E5 (after [AgentCore session] E1: Move the session-ID and stop steps of agentcore() into helpers #939, [AgentCore session] E4: Validate the agentcore_session config #942)
- [AgentCore session] E6: Add session.invoke #944 E6 (after [AgentCore session] E2: Move the job steps of agentcore() into a helper #940, [AgentCore session] E5: Add agentcore_session with the session lifecycle #943)
- [AgentCore session] E7: Label agentcore_session operations with a subtype #945 E7 (after [AgentCore session] E5: Add agentcore_session with the session lifecycle #943)
- [AgentCore session] E8: Add replay tests for agentcore_session #946 E8 (after [AgentCore session] E6: Add session.invoke #944)
- [AgentCore session] W1: Test several jobs in a row in one worker process #947 W1
- [AgentCore session] W2: Test the busy status with jobs in parallel #948 W2
- [AgentCore session] W3: Add the session ID and job count to worker logs #949 W3
- [AgentCore session] W4: Document sessions in the worker README #950 W4
- [AgentCore session] C1: Add a composed test of agentcore_session with the real worker #951 C1 (after [AgentCore session] E6: Add session.invoke #944, [AgentCore session] W1: Test several jobs in a row in one worker process #947)
- [AgentCore session] D1: Document agentcore_session in the extras README #952 D1 (after [AgentCore session] E6: Add session.invoke #944)
- [AgentCore session] X1: Add an agentcore_session example #953 X1 (after [AgentCore session] D1: Document agentcore_session in the extras README #952)
The twin epic is aws/aws-durable-execution-sdk-js#1245.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestneeds-triageIssue needs triageIssue needs triageprojectThe issues with an ongoing projectThe issues with an ongoing project
Activity
feat(extras): add the agentcore_session types (#960)