CHANGELOG

A little more capable.
With every step.

A record of what’s taking shape in Tubun, and a clear view of what comes next.

Development preview

These entries cover development milestones and preview releases. Check each entry and the download page for availability and validation status.

Community and local resources
PREVIEW

Share useful work. Make it your own.

0.1.0-preview.20261012.3

Move knowledge spaces, workflows, schedules, listeners and triggers between your local workspace and your community account. Preview imports before applying them; tasks and listeners stay paused until you configure them locally.

Author profiles, discussions and Stars give shared resources a place for questions and feedback. Self-contained, single-file Node.js MCP plugins can also be shared; imported plugins remain disabled until you review and enable them.

The Mac installer remains unsigned and not notarized. The Windows x64 installer is an unsigned test build; installation, startup, upgrades and uninstall still require validation on a Windows PC.

View downloads
Local installation
PREVIEW

A guided installation for your Mac.

A macOS PKG installer brings Tubun Agent to Applications with the existing product icon and a native launch window. The runtime is included, and application data remains separate during upgrades.

The package is smaller after removing duplicated front-end dependencies. Browser screenshots now save to the selected workspace and open through its existing file preview.

Apple Silicon and macOS 14 or later. This preview is unsigned and not notarized; clean-machine installation remains to be verified. Windows installation is still under validation.

View downloads
Workflow connections
NEW CAPABILITYWORKFLOWS

Give your workflow a window to the outside.

Listeners and triggers connect external messages to a workflow without turning the transport into another AI task.

  • Protocol templates for HTTP / Webhook, MQTT 5, and RabbitMQ / AMQP 0-9-1.
  • Gray external-system windows attach beside Start and End. Multiple listeners or triggers can attach to the same marker.
  • Declared message fields map into workflow inputs and can be selected by downstream tasks.
  • Execution records retain input, artifacts, and delivery status in the workspace.

Broker integrations require validation with your own environment. Transport or broker acknowledgement is distinct from a successful business update.

Read the integration guide
Interface refinement
IMPROVEDSETUP

A simpler way to set up a connection.

Common connection fields now live directly in the listener and trigger editor. A knowledge reference remains an optional configuration method.

  • Authentication and message settings can be expanded when needed.
  • The editor scrolls independently while keeping its main actions accessible.
  • Unsaved-change, delete, and token-reset confirmations use the application’s own dialogs.
  • Saved authentication values are preserved when editing or enabling a connection.
Configure a listener or trigger
Drawing & knowledge
EVOLVEDDRAWING STUDIO

Rules that fit the way your business works.

The drawing workflow brings templates, knowledge rules, and business inputs together, with a ventilation shutter scenario as a working example.

  • Component-level design rules can be organized around Frame, Louver, and Post, alongside assembly requirements.
  • Required upstream parameters are distinguished from reference values and design defaults.
  • Knowledge entries share a consistent editor for titles, node selection, text, and images.
  • Work files provides visual previews for SVG and DXF drawings.
Explore the workflow blueprint
LOOKING AHEADTeam Workflow
EARLY ACCESS DIRECTION

Shared tools. Clear ownership.

The next administrative experience is designed around the people using Tubun and the work they need to do.

  • User administration and allocation of features such as Drawing Studio, knowledge editing, and workflow design.
  • Central model configuration with visibility into actual API usage by user.
  • Assigned team knowledge alongside a separate place for personal reference.
  • Business-system workflows built around shared operating rules.

These are planned capabilities, not a delivery commitment. Scope and timing are agreed for each early access pilot.

Meet Team Workflow

Help shape what comes next.

Tell us about a real workflow your team wants to improve.

Start a conversation