Changelog

Released langchain-writer v0.1.0

• Updated tool binding to align with standard LangChain tool calling conventions.
• Added a new NoCodeAppTool tool for using no-code applications as tools.
• Added a new LLMTool tool for delegating to a specific Palmyra model.

See the guide to using the LangChain integration and the package documentation for more details.

New cookbooks for tool calling and no-code applications

We’ve added three new cookbooks to help you get started with no-code applications and tool calling.

• Generating content from no-code applications with the SDK
• Delegating a medical question to the palmyra-med model
• Using the Knowledge Graph chat tool

Palmyra Fin model updates

Palmyra Fin, our financial model, now has a 128k context window, up from 32k.

To use the Palmyra Fin model in the API and SDKs, use the palmyra-fin model ID. The palmyra-fin-32k model ID is now deprecated.

Released Writer LangChain integration

We’re excited to announce the first release of langchain-writer, the official Writer LangChain integration. This release includes:

• The ChatWriter model for text generation
• Tool calling capabilities, including the GraphTool for retrieving information from a Knowledge Graph
• Additional tools like the PDFParser for parsing PDFs and the WriterTextSplitter for intelligent text splitting

Check out the tutorial to get started and the full integration documentation for more details.

Released version 2.0.0 of the Python and Node SDKs

The 2.0.0 release includes new functionality for the Writer SDKs for Python and Node:

• Model delegation tool: A prebuilt, remotely executed tool that lets you delegate domain-specific requests to the appropriate Palymra model. For example, if your application has finance questions, you can use the tool to allow Palmyra X 004 to delegate these questions to Palmyra Financial. Read more in our model delegation guide.
• Retrieve application details: Retrieve details for all of your no-code applications. Programmatically retrieve application inputs rather than relying on the AI Studio UI. This pairs well with our guide on using no-code applications as tools.
• Async jobs: Trigger no-code application content generation asynchronously and retrieve or retry the job at a later time. This is great for long-running no-code applications, such as research assistant applications. To learn more, check out the guide on async jobs.
• Associate Knowledge Graphs with chat applications: Retrieve or update which Knowledge Graphs are associated with no-code chat applications.

See the SDK repositories for the full changelogs:

• Python
• Node

Python SDK

See below for the mapping of old types to new types:

Additionally:

• The types.chat_completion_chunk.Message type has been moved to its own model: types.chat_completion_message.

• types.chat.ChoiceLogprobsContent, ChoiceLogprobsRefusal, ChoiceLogprobsContentTopLogprob, and ChoiceLogprobsRefusalTopLogprob have all been deduplicated and replaced by a shared model types.shared.logprobs_token.LogprobsToken.

Node SDK

See below for the mapping of old types to new types:

The Node SDK includes developer experience improvements from Stainless, including using the native fetch API, resulting in zero SDK dependencies.

Released version 1.6.1 of the Python SDK

• Fixed a typing bug where the content field in the File did not accept the correct FileTypes values.

Released Python SDK version 1.6.0 and Node SDK version 1.5.0

• Added streaming support to the applications content generation endpoint and updated the No-code applications guide to reflect this.

Released Python SDK version 1.5.0

• Added new functionality via manual API updates
• Fixed compatibility with the latest httpx 0.28.0 release
• Improved handling of deprecated arguments (transport, proxies) to maintain backward compatibility
• Fixed compatibility issues with Pydantic model_dump method when warnings are passed
• Removed the now unused cached-property dependency, as we now rely on the standard library implementation for Python 3.8+
• Enhanced logging documentation in README, adding information about the ‘info’ log level
• Updated the recommended log level from ‘debug’ to ‘info’ for standard usage
• Fixed code formatting for better readability and consistency
• Excluded test files from mypy checks to avoid false positives
• Updated internal compatibility layer for better type checking
• Improved error handling for deprecated client configuration options

Released Python and Node SDK versions 1.4.0

• Updated the default timeout on the Writer client to three minutes.