JavaScript SDK Changelog

This page documents the release history of the Agentuity JavaScript SDK.

v0.0.145

Changes

• Fixed: Fix malformed From headers in email replies that caused parsing errors in backend (PR #174)

v0.0.144

Changes

• Fixed: Issues between streaming for node and bun and keep alive differences

v0.0.143

Changes

• Changed: Use traceloop for otel for consistency across Python and TS SDK's (PR #170)

v0.0.142

Changes

• Changed: Increase api timeout from 20 seconds to NEVER (PR #168)

v0.0.141

Changes

• Changed: Restructured slack IO and payloads (PR #164)
• Fixed: Fix email attachment parsing for Slack-formatted filenames (PR #160)
• Changed: Use sessionId instead of runId for AgentContext to better align with how we reference it (PR #165)

v0.0.140

Changes

• Fixed: Fix cloud runs for teams agents with improved credential validation and metadata-driven configuration (PR #162)

v0.0.139

Changes

• Added: Teams support (PR #161)

v0.0.138

Changes

• Fixed: Fix the sms error (PR #158)

v0.0.137

Changes

• Added: Expose ts and ts_thread in the payload for Slack IO integration (PR #157)

v0.0.136

Changes

• Changed: The AgentResponse.stream() method now supports both function and generator transformers while maintaining full backward compatibility! The enhancement includes:

  Original Requirements:

  • Generic object streaming with automatic JSON conversion
  • Runtime type detection between ReadableDataType and objects
  • Auto-conversion to JSON newline format for objects
  • Intelligent content-type detection (application/json for objects)
  • Full backward compatibility

  Function Transformer Enhancement:

  • Optional transformer function as 4th parameter
  • Data transformation and filtering capabilities
  • Type safety with generic types
  • Error handling and edge cases

  Generator Transformer Enhancement:

  • Support for generator functions as alternative syntax
  • One-to-one transformation with yield syntax
  • Filtering support: generators can yield nothing to skip items
  • Same capabilities as regular functions but with generator syntax

  Key Benefits:

  • Maximum Flexibility: Choose between function or generator syntax
  • Developer Choice: Use familiar function syntax or expressive generator syntax
  • Consistent Behavior: Both approaches work identically
  • Type Safety: Full TypeScript support with generic types
  • Performance: Efficient one-to-one transformations
  • Backward Compatibility: Existing code continues to work unchanged

  Test Coverage:

  • 26 test cases covering all functionality
  • Function transformer scenarios (8 tests)
  • Generator transformer scenarios (7 tests)
  • Backward compatibility verified
  • Error handling tested
  • Mixed scenarios validated
  • Both ReadableStream and AsyncIterable support

  Files Modified:

  • src/types.ts - Enhanced interface with generator support
  • src/router/response.ts - Full implementation with generator detection and processing
  • test/router/response-stream.test.ts - Comprehensive test coverage

  The Agentuity SDK now provides the most flexible and powerful streaming API that supports object auto-conversion, intelligent content-type detection, data transformation, filtering, and both function and generator transformer syntaxes! (PR #155)

v0.0.135

Changes

• Added: Slack IO integration with support for parsing and replying to Slack messages (PR #153)

v0.0.134

Changes

• Added: Telegram IO integration with support for parsing and replying to Telegram messages (PR #151)

v0.0.133

Changes

• Added: Enable the ability to use custom email domains for email replies (PR #149)

v0.0.132

Changes:

• Changed: DevMode fallback values for headers, url and method in metadata (PR #148)

v0.0.131

Changes:

• Added: Support for bulk delete in vector storage - The vector.delete() method now accepts multiple keys as variadic arguments, allowing efficient bulk deletion of vectors. Supports both single key deletion (delete(name, key)) and bulk deletion (delete(name, key1, key2, key3)) patterns. This is more efficient than making multiple individual delete calls. (PR #145)
• Changed: Improved documentation of vector search parameters and tightened vector search metadata type definition (PR #146)

v0.0.130

Changes:

• Changed: Shortened Discord interface from discordMessage to discord for improved usability (PR #144)

v0.0.129

Changes:

• Added: Discord IO integration with support for parsing and replying to Discord messages (PR #130)
• Fixed: Release stream lock in all cases especially error scenarios (PR #136)
• Fixed: Issue with handoff not passing data from previous request (PR #139)

v0.0.128

Changes:

• Fixed: Release stream lock in all cases especially error scenarios (PR #136)

v0.0.127

Changes:

• Added: SMS Twilio IO functionality with support for parsing and replying to SMS messages (PR #124)

v0.0.126

Changes:

• Added: Enhanced ObjectStore API with additional headers and metadata support (PR #133)
• Changed: Better handling for yield / generators (PR #134)

v0.0.125

Changes:

• Added: Support for new object store API
• Fixed: Description for similarity property for vector search
• Fixed: Issue with incorrect type for Vector delete API

v0.0.124

Changes:

• Changed: Refactored Bun handler to consolidate logic and ensure all paths go through unified method (PR #128)

v0.0.123

Changes:

• Fixed: Improved handling of requests for common static files and enhanced support for multiple path segments and different HTTP methods (PR #126)

v0.0.122

Changes:

• Added: Support for large email attachments (PR #123)

v0.0.121

Changes:

• Added: Support for agents to be able to reply to incoming email (PR #118)

v0.0.120

Changes:

• Added: Support for handling inbound email trigger type (PR #117)

v0.0.119

Changes:

• Logger message arg accepts number type (PR #113)
• Prevent multiple logs for the same exception (PR #115)

v0.0.118

Changes:

• Improve error handling (PR #111)

v0.0.117

Changes:

• Improvement: Better type handling for metadata where it can be any valid JSON object (PR #110)

v0.0.116

Changes:

• Fixed issue where empty POST body would cause a hang (PR #109)

v0.0.115 ⚠️

Changes:

• Added AGENTUITY_SDK_KEY (PR #107)

⚠️ Breaking Changes

The environment variable AGENTUITY_API_KEY has been renamed to AGENTUITY_SDK_KEY for better clarity and consistency. You will need to update your environment variables and code references accordingly.

If you're using the Agentuity CLI, it will detect this change and offer to automatically migrate your code references for you.

For example, you'll need to make the following changes in your code and environment variables:

- process.env.AGENTUITY_API_KEY
+ process.env.AGENTUITY_SDK_KEY

If you're using an Agentic code editor (such as Cursor, Windsurf, etc.), you can use this prompt to update your code with these changes:

The Agentuity SDK v0.0.115 has renamed AGENTUITY_API_KEY to AGENTUITY_SDK_KEY.
Please find all instances of AGENTUITY_API_KEY in my code and replace them with AGENTUITY_SDK_KEY.

v0.0.114

Changes:

• Fixed issue with Vector get type being wrong (PR #106)

v0.0.113

Changes:

• Cross platform support for headers.toJSON (PR #105, resolves #103)

v0.0.112

Changes:

• Add a bun server handler to handle unhandled errors (PR #100)
• Add missing console methods (PR #101)

v0.0.111

Changes:

• More fixes related to gzip compression when using keyvalue
• Change the name of the span when doing a remote solution vs remote execution
• Update to use versioned routes for API services (PR #97)

v0.0.110

Changes:

• In cloud we must bind to all addresses (PR #96)

v0.0.109

Changes:

• Add the ability for an agent to return a Response object directly to provide more flexibility to integrate with existing APIs and protocols (PR #93)
• Bind explicitly to ipv4 when creating server (PR #94)

v0.0.108

Changes:

• Fixed issue when the keyvalue returns a gzip encoded value (PR #92)

v0.0.107

Changes:

• Fix issue with chunking and streaming text not matching in some cases (PR #91)

v0.0.106 ⚠️

Changes:

• Add support for streaming data to and from agents. This includes streaming data to the agent via the data object and streaming data from the agent via the stream property of the AgentResponse object.
• The trigger property of the AgentRequest object will have the value agent when the request is invoked by another agent.
• The AgentContext object now has a scope property that will have the value of local when the context is local or remote when agent is being invoked by another agent remotely. In the case of agent-to-agent invocation or handoff within the same project, the scope will be local.
• Deprecated the local /run/:agentId route since the updated /:agentId route now supports streaming data to and from the agent directly. This route will be removed in a near future release.

⚠️ Breaking Changes

The data object of AgentRequest has changed to support fully streaming data and this required a breaking change. Most of the property accessors are now async functions to support the streaming use case. You can read more about this change in Pull Request #87.

For example, the following code changes are required to get the request data as text:

- const text = req.data.text;
+ const text = await req.data.text();

For example, to get the request data as JSON, you need to make the following changes:

- const json = req.data.json;
+ const json = await req.data.json();

See the following documentation Pull Request for specific SDK changes.

If you're using an Agentic code editor (such as Cursor, Windsurf, etc.), you can use this prompt to update your code with these changes:

The agents in the agents folder use an older version of the Agentuity SDK which assume the req.data object has properties on it like req.data.json

The new way to do this is with a promise. eg. `await req.data.json()`

The breaking change is here:  https://github.com/agentuity/sdk-js/pull/87

Review this PR, make a plan to change the agents to the latest agentuity SDK with async await support, and execute on it.

v0.0.105

Changes:

• Add support for remote agent handoff (PR #85). This means you can now handoff the request to another agent outside of your current project in the same organization or even outside of your organization if the Agent is public. The agent-to-agent invocation is secured automatically and doesn't require any additional configuration or authentication. Internally, the SDK will request a one-time authorization token to invoke the agent on your agent's behalf.

v0.0.104

Changes:

• Add support for remote agent-to-agent invocation (PR #83). This means you can now invoke another agent outside of your current project in the same organization or even outside of your organization if the Agent is public. The agent-to-agent invocation is secured automatically and doesn't require any additional configuration or authentication. Internally, the SDK will request a one-time authorization token to invoke the agent on your agent's behalf.

v0.0.103

Changes:

• Refactor to support binary streams instead of intermediate JSON protocol (PR #81)
• Improved handling of HTTP native protocol
• Added support for passing in the runId
• Better handling of stream data and binary content

v0.0.102

Changes:

• Fix issue where the child span had the wrong parent on outbound requests for agent-to-agent (PR #79)

v0.0.101

Changes:

• Add agent context to console logger when running inside agent scope (PR #77)

v0.0.100

Changes:

• Add permissions
• Add more otel trace context headers, remove old trace provider (PR #72)
• Automatically base64 encode welcome prompts (PR #73)
• Fix NodeJS issue where the buffer isn't correctly sending the blob but works fine in Bun version (PR #74)
• Debug github workflow git tag issue

v0.0.99

Changes:

• More debug for github workflow

v0.0.98

Changes:

• More debug for github release tags

v0.0.97

Changes:

• Attempt to fix issue with github workflow not pushing tag after release

v0.0.96

Changes:

• Fix issue with node keyvalue not correctly handling the buffer upload

v0.0.95

Changes:

• Add more otel trace context headers, remove old trace provider
• Base64 encode the welcome prompts

v0.0.94

Changes:

• Fix regression in otel traces missing for AI SDK by change in opentelemetry-api version change

v0.0.93

Changes:

• Add support for agent inspection discovery (PR #70)

v0.0.92

Changes:

• Add data and markdown methods to AgentResponse interface and implementation

v0.0.91

Changes:

• Use new agentuity sdk api
• Add GitHub workflow for npm package release triggered by version tags (PR #53)

v0.0.90

Changes:

• Fix Vector delete api

v0.0.89

Changes:

• Add the agentName to the log attributes (PR #33)
• Console Logger: show max depth for any objects (PR #32)
• When stream is requested but the response isn't a stream, chunk up the response data into chunks and smooth out as if streamed (PR #31)
• Fixed issue with buffer underrun getting sent and issue with json encoding (PR #34)

v0.0.88

Changes:

• Improve loading project when using node or bun directly vs using start script or agentuity dev
• Fix mismatch between local run vs remote run with HTTP headers as property of metadata vs the metadata object

v0.0.87

Changes:

• Slight improvement in location of when context.logger for agent is created

v0.0.86

Changes:

• Add support for agentId on context.logger
• Fix issue with underrun on base64 stream

v0.0.85

Changes:

• Streaming Support including SSE

v0.0.84

Changes:

• Stream IO Input: add new facility to support stream io for input data (PR #23)
• Release with new transport model

v0.0.83

Changes:

• Fix devmode logging when devmode environment is set by live (PR #24)

v0.0.82

Changes:

• KeyValue compression only on upload, not download (PR #20)

v0.0.81

Changes:

• Add support for compressing keyvalue entries (PR #19)
• Better format log message if the first parameter is an object (PR #18)

v0.0.80

Changes:

• Refactored the types to make it easier to use
• Fixed various small issues

v0.0.79 and earlier

For earlier versions, see the CHANGELOG.md file in the repository.