Tukuan.ai 0.11 Is Live: Back to One Main Path

Tukuan.ai 0.11 is now live.

This release brings model selection, billing, file upload, and in-product notices onto one product path. The result is simple: Tukuan.ai feels more like a usable analytics product and less like a bundle of adjacent systems.

0.10 established the account, identity, and isolation baseline. 0.11 moves those foundations into user-visible product behavior: you can work inside one workspace, rely on plan-aligned model selection, see billing state that reflects what actually took effect, start analysis from uploaded files, and keep important notices inside the product.

What 0.11 changes

The headline of 0.11 is not a single feature. It is that several previously separate concerns now behave more like one product:

• model selection is constrained by the current plan
• billing state reflects confirmed outcomes instead of checkout redirects
• uploaded files enter the same Workbench path as other analysis inputs
• operational notices and account announcements become durable inbox history

For users, that means less guessing. You do not need to switch between different entrypoints, different status rules, and different save paths just to understand what the product considers true.

Plan-aware model selection

Before 0.11, model selection still felt partly like infrastructure wiring. In 0.11, it becomes a clearer product rule.

Users can still choose auto, but auto is no longer a vague default. The system resolves it against the active account plan, picks an allowed baseline model, and only steps up when the task actually needs stronger capability.

The practical benefit is straightforward:

• the model experience stays aligned with the plan
• users do not need to manage raw model and provider complexity themselves

We want model choice to feel like product behavior, not like low-level provider configuration.

Billing that behaves like product truth

0.11 also moves the commercial path onto the current Paddle production flow.

This release adds Paddle checkout, billing portal integration, billing summary surfaces, and ledger visibility. More importantly, it reinforces a simple rule: plan and billing state should reflect confirmed outcomes, not a temporary checkout redirect.

That may sound like backend detail, but it is really about product trust. If plan state, credits, and subscription status are unreliable, then model access and usage limits feel unreliable too.

For users, the change is simple: the billing state you see in the product should better match what has actually taken effect.

Uploaded files become first-class inputs

One of the most important 0.11 changes is that uploaded files are no longer treated like a side flow.

CSV and XLSX files can now enter directly through the current upload mode and come back into the normal Workbench timeline as part of the conversation. In Cloudflare Worker deployments, the release also adds direct R2 upload mode with signed sessions and resumable multipart upload support.

For users, this means you can start analysis from a file more naturally, instead of going through one upload path and then switching into a separate analysis path.

We have wanted Workbench to remain one main path. File input now fits that path much better.

Inbox, maintenance notices, and account announcements

0.11 also adds a more durable communication layer inside the product.

The new /inbox surface becomes the in-app message center with unread counts, read and dismiss actions, and header preview integration. On top of that, platform maintenance notices can now appear in both the global notice bar and inbox history. Eligible non-personal account admins can also publish account announcements to their current members.

This is not just UI polish. It gives the product a stable place for operational history and account communication instead of pushing important information into short-lived toasts or one-time page notices.

For users, it means important notices are less likely to disappear after one glance.

Hardening the governed path

Beyond the visible features, 0.11 continues a lot of product hardening work:

• semantic discovery drafts continue moving toward a more stable authoring flow
• dashboard refresh now returns inspectable error information instead of failing opaquely
• billing idempotency, webhook retry, and final-state handling are stricter
• upload validation, session startup, and pipeline integrity checks are stronger
• inbox state sync and recovery paths from deep links are more reliable

These are not demo features, but they are the details that decide whether a product feels stable in repeated real use.

Why this release matters

For us, 0.11 is the point where several foundational systems stop feeling like adjacent implementation tracks and start behaving more like one coherent product.

Users can now get a more consistent model experience, see billing state that is easier to trust, bring files into the same analysis path, and receive durable in-product communication without breaking the single-workspace model.

That is what makes 0.11 a productization release.