T-Builder is now Rekhu Builder, and every site lives in its project
The builder carries the Rekhu name, and the account has one place per site or app. A project now holds its chat, its connection, its keys and its assistant, for WordPress sites, Laravel apps and Node.js apps.
T-Builder has a new name: Rekhu Builder. It is the same builder, for WordPress sites and Laravel apps, and it now carries the name of the platform it runs on. Next to it is Rekhu Assistant, the assistant you build into your own app for your own customers.
One place per site or app
Until now, a site's key lived on one page of the account and its work on another. From today, everything about a site or an app is in its project.
New project asks what it is: a WordPress site, a Laravel app or a Node.js app. For an app you also choose its architecture:
- Monolith: one app with its users.
- Multi-tenant: one app serving many tenants, each with their own users and data.
The key is made together with the project.
Every project has these tabs:
- Chat: work with Rekhu Builder on the site or app, as before.
- Connection: the plugin or package to install, the key (a new one in one click if it is lost), the tool switches, and for an app the assistant's keys per environment.
- Assistant: for Laravel and Node.js apps. Usage per user (monolith) or per tenant (multi-tenant), a CSV to bill from, a monthly limit and a pause.
The Apps page is gone; what it held now lives in the projects. A site that is connected but not yet in a project shows at the top of Projects, with one click to give it one. Deleting a project now also blocks its keys.
For multi-tenant Laravel apps
When a Laravel project is multi-tenant, Rekhu Builder first finds how tenancy is set up: the package, how a tenant is identified, which routes and databases are central and which belong to a tenant. It then works inside a tenant's context and says which tenant a finding concerns.
Rekhu Builder 0.9.36
The plugin says Rekhu Builder in the WordPress menu, the plugin list, the settings, the widgets and its messages, and points to the project's Connection tab for its key. Its folder stays t-builder, so it updates from the account as usual and nothing on the site changes.
The assistant packages
rekhu/assistant-laravel 0.3 rebuilds the chat endpoints:
- errors, including an expired sign-in, now come back as JSON the widget can show;
- the messages your users read can be translated;
- the package is tested on PHP 8.2 to 8.4 with Laravel 12 and 13.
@rekhu/assistant-node 0.2.1 points its log to the project's Assistant tab.