Skip to content

Talisman 26.16.0

Talisman 26.16.0 brings Studio for VS Code, Talisman AI that works on your integration projects, and MCP servers built as integrations. It also makes test and production environments lighter to run. Integrations run on Apache Camel 4.22 and Java 25.

Studio for VS Code (preview)

The Talisman designers now run inside Visual Studio Code. You design, run and ship integrations from your own git repository and your own CI/CD.

  • Visual designers: the Topology Designer, the Route Designer for routes and Kamelets (the full Apache Camel 4.22 catalog), OpenAPI, JSON Schema and PLC (Siemens S7). Everything is saved as plain YAML or JSON, so you can edit in the designer or the text editor, side by side.
  • Run and observe locally: run a project on Docker or a local Kubernetes cluster and see changes without a restart. A live runtime panel shows routes, statistics, errors with the failed message, traces and JVM health. Try out APIs and MCP servers against the running project, and start ready-made dev services such as Kafka, PostgreSQL and ActiveMQ Artemis.
  • Build and deliver: build a container image and push it to your registry, or add a CI/CD pipeline for GitHub Actions or Azure Pipelines in a few clicks. You can also promote a build between environments and export a project as a zip archive.
  • Smart editing: completion, validation and one-click fixes for Apache Camel configuration and Groovy scripts, including renamed and removed options.
  • Try it free: a 30-day trial on first use, with no sign-up. The license file is checked on your machine, and Studio sends no telemetry.

Install it from the VS Code Marketplace (talisman-platform.talisman-studio). See Studio for VS Code and the Development & Deployment Principles for the two ways to use it: VS Code with Server Build and VS Code with CI/CD.

Talisman AI

Talisman AI works in both Studio Web and Studio for VS Code, with your own Anthropic, Google Gemini or OpenAI key.

  • A coding agent that plans, writes, validates and runs a change in your project.
  • Task templates for common work: new routes, Groovy scripts, SQL, Apache Camel upgrades and more.
  • Watch the AI's work live in the project topology. It asks questions or shows a form when it needs input.
  • Protect each project with its own AI password, and block components the AI may not use.
  • Sensitive values are masked in AI session records.

MCP servers as integrations

Build Model Context Protocol (MCP) servers the same way as any other integration: Apache Camel routes implement the tools, resources and prompts.

  • An MCP designer to declare tools, resources and prompts, with OAuth support.
  • MCP TryOut in Studio Web and Studio for VS Code.
  • MCP servers and AI agents appear in the Development Dashboard and the project topology.

Lean servers for test and production

Test and production instances of Talisman Server can run without git, and with OpenID Connect also without a database. They show the running integrations read-only and keep full monitoring, health checks and self-healing.

Talisman Server and Studio Web

  • Deploying to Kubernetes: per-environment overrides are merged into the deployment, redeploying a running integration does a rolling update, and the confirmation shows exactly what will be applied.
  • Promotion: build once and promote the same image and manifest from development to test to production.
  • Image signing: optionally sign container images with Cosign.
  • Better visibility: pod events, containers and images per project, errors from running integrations, and an interactive Apache Camel developer console (including SQL).
  • Monitoring for older integrations: integrations still on Apache Camel 4.18 are monitored and healed too.
  • Docker: set resource limits and reservations for containers. Images are built for the host's architecture (amd64 or arm64).
  • Version control: revert a project to any earlier commit.
  • Topology: project size and route count, and a Kamelets list.
  • Refreshed look: new monochrome Apache Camel component icons.

Developer tooling

  • Project validation: checks routes (including component options), Groovy, SQL, OpenAPI contracts and references between files before you run or build.
  • Apache Camel upgrade assistant: moves projects from Apache Camel 4.10, 4.14 or 4.18 to 4.22 (and Java 21 to Java 25) in one step. It reports what changes, applies the safe fixes automatically, and Talisman AI handles the rest.
  • CI builder image: talisman-builder builds and deploys Talisman projects in your own CI with the same tooling Talisman uses. See CI/CD Build.
  • Faster startup for the developer-mode and build images.

Platform

  • Versions: Apache Camel 4.22.2 on Apache Camel Main, and Java 25 for both Talisman and your integrations.
  • Naming: the product names are now Talisman Server (with Studio Web) and Studio for VS Code; together, Studio Web and Studio for VS Code are Talisman Studio.

Upgrading to 26.16.0

  • Apache Camel projects: projects on Apache Camel 4.10, 4.14 or 4.18 should run the upgrade assistant (check, then apply), then validate and test before deploying on 26.16.0.
  • Docker Swarm: support is discontinued. Run integrations on Docker or Kubernetes.
  • Ingress: integration projects no longer create a Kubernetes Ingress. Expose external endpoints through your API gateway or ingress controller.

Happy Integrating!