Skip to main content

​
Platform (Studio)

  • Workflow builder chat now works with reasoning models served through a self-hosted openai-compatible gateway, instead of failing with a “temperature is not supported” error. On models that only accept their own default temperature setting, replies can vary between attempts on the same question.
  • Canonical API hostnames now consistently expose only supported API and operational routes, returning a clear 404 for unsupported discovery paths.
  • Agent Builder attachments now negotiate multipart or storage-direct transfer, so large PDFs and archives can reach the active sandbox without crossing cloud payload limits. Large downloads use the same secure dual path. Self-hosted operators can set deployment.multipartMaxBytes in eigenpal.config.yaml; the supplied on-prem deployments keep files on multipart and streamed downloads by default.
  • Canonical API hostnames now serve API routes and discovery endpoints reliably without Studio sign-in handling intercepting requests.

​
Public API

  • Upload and download reusable files up to 100 MiB through one negotiated API: files within the deployment body limit use multipart, while larger cloud transfers use verified storage-direct uploads and short-lived authenticated download links. Retry-safe temporary run and Builder files expire after 24 hours. Existing multipart routes and studio.eigenpal.com/api/v1 remain compatible, and new integrations can use api.eigenpal.com/v1.

​
CLI

  • The CLI now uses api.eigenpal.com as the default cloud API origin and automatically pre-uploads run files that exceed the multipart request limit. Self-hosted users can keep custom API origins and set EIGENPAL_MULTIPART_MAX_BYTES to their proxy limit, or none to keep all files on multipart.

​
SDK

  • The TypeScript and Python SDKs now transparently upload large run inputs without crossing cloud request limits, follow secure storage-direct downloads, and default cloud calls to api.eigenpal.com. Set multipartMaxBytes / multipart_max_bytes, or EIGENPAL_MULTIPART_MAX_BYTES, to match a self-hosted proxy; use null / None to keep every run file on multipart. Explicit files.upload files remain reusable until deleted.
  • TypeScript file uploads now follow the server-negotiated multipart endpoint, improving compatibility across hosted and self-managed route layouts.

​
Infrastructure & processing

  • Extraction steps now run on reasoning models served through a self-hosted openai-compatible gateway, instead of failing with a “temperature is not supported” error. On models that only accept their own default temperature setting, output can vary slightly between runs of the same input.