[bot] Instrument AWS Bedrock AgentCore (876,384 weekly downloads)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- aws, typescript
- Domain
- observability
Research direction
Start by comparing the existing Bedrock integration in js/src/wrappers/bedrock-runtime.ts, js/src/instrumentation/plugins/bedrock-runtime-plugin.ts, js/src/instrumentation/plugins/bedrock-runtime-channels.ts, and js/src/auto-instrumentations/configs/bedrock-runtime.ts. Then inspect js/src/auto-instrumentations/configs/all.ts and the e2e/scenarios/ directory for integration patterns. Done means AgentCore runtime invocation and session lifecycle coverage is registered and exercised by an end-to-end scenario.
Written by the indexing model from the issue text.
Description
<!-- library-gap-audit: aws-bedrock-agentcore -->
Summary
Amazon Bedrock AgentCore is AWS's dedicated agent-hosting/runtime service (distinct from both the model-invocation Bedrock Runtime and the RAG-oriented Bedrock Agent Runtime). Its official JS/TS client, @aws-sdk/client-bedrock-agentcore, exposes InvokeAgentRuntimeCommand — the core "run an agent and stream its output" execution API — plus session-management commands (e.g. StopRuntimeSessionCommand). None of this is instrumented in this repository.
What's missing
InvokeAgentRuntimeCommand(package@aws-sdk/client-bedrock-agentcore) — invokes a deployed AgentCore Runtime agent by ARN, optionally with a session ID for multi-turn continuity, and returns a streaming response (contentStart/contentDelta/contentStopevents) with the agent's output. This is the primary agent-execution surface of the service.- Session lifecycle commands (e.g.
StopRuntimeSessionCommand) that bound an agent-run session.
This is a separate npm package and separate AWS service from what's already instrumented here: js/src/wrappers/bedrock-runtime.ts and js/src/instrumentation/plugins/bedrock-runtime-plugin.ts / bedrock-runtime-channels.ts only cover @aws-sdk/client-bedrock-runtime (raw model invocation, e.g. InvokeModelCommand/ConverseCommand). A repo-wide case-insensitive search for bedrock-agentcore, AgentCore, and InvokeAgentRuntime returns zero matches anywhere in js/src/, js/src/auto-instrumentations/configs/all.ts (the full instrumentation registry), or any e2e/scenarios/* directory.
Weekly downloads
Weekly downloads: 876,384 (as of 2026-09-28; window 2026-09-20–2026-09-26; source https://api.npmjs.org/downloads/point/last-week/@aws-sdk/client-bedrock-agentcore).
Braintrust docs status
not_found — checked both https://www.braintrust.dev/docs/integrations and https://www.braintrust.dev/docs/guides/tracing/integrations. Both pages list "AWS Bedrock" generically but neither mentions "AgentCore," "Bedrock AgentCore," or the AgentCore runtime/session APIs anywhere.
Upstream sources
- https://www.npmjs.com/package/@aws-sdk/client-bedrock-agentcore
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-invoke-agent.html
- https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-bedrock-agentcore/
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-toolkit-typescript.html
Local repo files inspected
js/src/wrappers/bedrock-runtime.ts,js/src/instrumentation/plugins/bedrock-runtime-plugin.ts,js/src/instrumentation/plugins/bedrock-runtime-channels.ts,js/src/auto-instrumentations/configs/bedrock-runtime.ts— confirm only@aws-sdk/client-bedrock-runtimeis coveredjs/src/auto-instrumentations/configs/all.ts(full instrumentation registry — no AgentCore entry)- Repo-wide case-insensitive search for
bedrock-agentcore,AgentCore,InvokeAgentRuntime(no matches) e2e/scenarios/directory listing (no AgentCore-named scenario)
- Dominant language
- TypeScript
- Stars
- 28
- Forks
- 15
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 73
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from braintrustdata/braintrust-sdk-javascript
-
typescript
Difficulty 4/5 3-5 days Newbie friendliness 55/100
braintrustdata/braintrust-sdk-javascript#2578 ·
Maintainers usually reply within 2 days
-
typescript
Difficulty 4/5 3-5 days Newbie friendliness 55/100
braintrustdata/braintrust-sdk-javascript#2577 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
braintrustdata/braintrust-sdk-javascript#2527 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
braintrustdata/braintrust-sdk-javascript#2482 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
braintrustdata/braintrust-sdk-javascript#2481 ·
Maintainers usually reply within 2 days
All issues in braintrustdata/braintrust-sdk-javascript
Similar issues
-
Bump Firebase JS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
invertase/react-native-firebase#9364 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 4 days
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/rhdh-plugin-export-overlays#4261 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug] 官网文档的图片挂了Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area:cli bug triage:in-progress
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day