This release focuses on improving OpenAPI components and introducing two test agents to that end.

SchemaForge & SkillsForge #439 #436 #437

SchemaForge & SkillsForge are agents configured to use IX's internal API to manage schemas (#400) and skills (#420 ). These agents both use RunOpenAPIRequest and provide create, read, update, and delete functionality.

These agents are both an easy way to create new skills and a good test bed for OpenAPI and agent functionality.

OpenAPI & Function Calling Improvements

• RunOpenAPIRequest now includes descriptions from schema description and fields in tool schema passed to OpenAI. #431
• Schema description now included in function schema when used as a tool. #432
• RunOpenAPIRequest now has a separate instructions field for extra instructions to pass in the tool function schema #433
• RunOpenAPIRequest now properly handles paths with variables in them.
• RunOpenAPIRequest now returns response.json for HTTP errors rather than raising errors. Allows agents to reflect on the errors. #438
• Agents may now be configured to reflect on parsing errors and correct them.
  #440

Misc

• LangChain 0.1.5 #430
• Node config forms were spamming save notifications. This should be improved. #441
• Prop and link edges are now styled differently #429
• Hide node config sections if they do not contain any properties #434
• updated IX API fixtures for minor changes to support SchemaForge and SkillsForge #442

Misc fixes:

• Added a better dark theme for the CodeEditor

Bugfix release:

• The first node dropped on a new flow couldn't be edited #427

Skills

Skills are components that may be created through the UI and API. Skills may be called as tools or used as a node in a flow.

Skills are defined as typed python functions so they are easy to build. Input/Output types and schemas are generated from the methods type hinting.

Skill Editor

Prototype SkillForge agent

An unreleased SkillForge prototype agent that generates skills that may be used in other flows

Rich code editor

A rich code editor was added to support the skilll editor. It has also been applied to the JSON Schema editor. It will eventually support other places where code is rendered or edited.

Misc

• fixed a number of dependabot vulnerability warnings

A small release that includes a new JSONTransform component to simplify flow and a number of bug fixes for the editor.

JSON Transform #411

Introducing JSONTransform an advanced version of JSONPath that can build lists and objects in addition to single values. It's a flexible way to extract multiple values and build more complex values.

JSONTransform can replace many instances where JSONPath and Map were chained to pack a value in a dict. Shown here in the dall-e agent.

Previous Dall-e agent

Updated Dall-e agent

Misc

• Run log viewer now renders input/output with json highlighting #412
• Run log viewer now expands to fill the modal #412
• ChainSelect now shows initial values loaded from API and renders a custom option #413
• Nodes now have a context menu containing action features like delete and open-in-tab #415
• Referenced chains may now be opened in a new tab via the context menu. #415

Bug Fixes

tab state syncing

• Edge create/update/delete was not synced to tab state #416
• Node delete was not synced to tab state #416
• Edge updates weren't synced if they only moved between keys on the source or target #417

misc fixes

• JSON Schema didn't appear when dropped on the graph. #414

Bug fixes

• Nodes that were edited were reverting to their original values when clicking back and forth between them. #410

This release focuses on a new data module that includes an API and storage for JSON Schemas & OpenAPI Specs. Both include components to utilize them in flows.

JSON Schemas #387 #299 #391 #393 #398 #399

JSON Schemas may now be created through the UI. Schema objects are usable within the flow as an input or as a function with LLMs that support function calling.

Components:

• SaveSchema - generate new schemas with the SaveSchema component
• LoadSchema - loads schemas from the registry.

JSON Form inputs:

• JSONSchemaSelect

OpenAPI Specs #387 #391 #394 #398 #408

OpenAPI specs may now be imported using a URL. Use them in flows as tools or as regular chains to interact with remote APIs.

The editor provides a viewer for the spec's endpoints and schemas. Action specs may be dragged onto a flow to create a preconfigured OpenAPI Request.

Components:

• OpenAPI Request - load a schema and run a request.

JSON Form inputs:

• OpenAPISchemaSelect
• SchemaActionSelect
• SchemaServer

Drag-n-drop objects #400 #405 #409

Many objects may now be dropped into the graph as preconfigured nodes. This is built on a new DraggableNode wrapper that simplified mapping types to nodes.

• JSON schemas
• OpenAPI specs & actions
• Chains

Fixes for tabs and new chains #391 #395 #397

There were still quite a few gremlins in the new state management for tabs. This caused various issues with nodes not appearing when saved, values reverting after saving, crashes, etc. Many bugs were fixed during the testing of this version.

Misc

• Most edits within the editor now show a toast message on success #396
• Generalized react-select components and hooks for easier re-use #388
• LangChain 0.1.0 #390
• Add JSONSchemaDisplay for rendering specs #401
• Nodes now appear mostly centered on the header when dropped #403
• API endpoints have simplified operation_id for better integration with OpenAPI Request nodes #406
• menu style now better configured #407

This release focuses on a new data module that includes an API and storage for JSON Schemas & OpenAPI Specs. Both include components to utilize them in flows.

JSON Schemas #387 #299 #391 #393 #398 #399

JSON Schemas may now be created through the UI. Schema objects are usable within the flow as an input or as a function with LLMs that support function calling.

Components:

• SaveSchema - generate new schemas with the SaveSchema component
• LoadSchema - loads schemas from the registry.

JSON Form inputs:

• JSONSchemaSelect

OpenAPI Specs #387 #391 #394 #398 #408

OpenAPI specs may now be imported using a URL. Use them in flows as tools or as regular chains to interact with remote APIs.

The editor provides a viewer for the spec's endpoints and schemas. Action specs may be dragged onto a flow to create a preconfigured OpenAPI Request.

Components:

• OpenAPI Request - load a schema and run a request.

JSON Form inputs:

• OpenAPISchemaSelect
• SchemaActionSelect
• SchemaServer

Drag-n-drop objects #400 #405 #409

Many objects may now be dropped into the graph as preconfigured nodes. This is built on a new DraggableNode wrapper that simplified mapping types to nodes.

• JSON schemas
• OpenAPI specs & actions
• Chains

Fixes for tabs and new chains #391 #395 #397

There were still quite a few gremlins in the new state management for tabs. This caused various issues with nodes not appearing when saved, values reverting after saving, crashes, etc. Many bugs were fixed during the testing of this version.

Misc

• Most edits within the editor now show a toast message on success #396
• Generalized react-select components and hooks for easier re-use #388
• LangChain 0.1.0 #390
• Add JSONSchemaDisplay for rendering specs #401
• Nodes now appear mostly centered on the header when dropped #403
• API endpoints have simplified operation_id for better integration with OpenAPI Request nodes #406
• menu style now better configured #407

Bugfixes:

• Knowledge agent is no longer broken. #389

Editor Tabs

The flow editor now has tabs to open multiple chains/agents. This should help user's manage context while working on nested chains simultaneously.

Misc:

• Component search popup now supports SVGIcon and other minor styling fixes. #385
• Run log now renders component type info for components newly added to the flow #384