A history of notable AiHummer changes. The current line is v1.0.x. Each
entry below carries its date and the components it touched; the
upgrade guide explains how to move up.
[!NOTE]
This page lists changes that matter to users and administrators. The exact
build version is visible in the Admin UI and in the
API explorer (Swagger).
v1.0.17 (Core, stable) — 2026-08-02
Fixed
Web search now really starts on a fresh install: its settings are written
before the readiness check and it gets a freshly generated secret key, so the
service no longer refuses to run with the default one.
Node.js now ships inside the bundle and installs offline, so plugins that need
it — the AiHummer app, pocket-agent and the channel connectors — install on
distributions whose own Node.js is too old.
A release no longer fails because a large download is merely slow: transfers
resume where they stopped and are aborted only when they actually stall.
Changed
aihummer status now closes with next steps chosen for what it found: a
gateway that is down leads with its journal, a healthy one with diagnostics,
settings and the documentation. Only real commands are suggested.
v1.0.16 (Core, stable) — 2026-08-02
New
A knowledge source can now belong to one AI employee or be shared by all of
them, and retrieval respects that binding.
Changed
The AiHummer app plugin moves to the published 1.0.4 release, which carries
the device sign-in fixes.
Fixed
A fresh install no longer stops right after unpacking the bundled browser: an
optional sidecar can never abort the installation, so the gateway, the
database and every plugin are set up as intended.
The bundled web search now starts on hosts with Python 3.12, and the bundled
browser gets the system libraries it needs; a missing library is reported
honestly instead of leaving the service in a restart loop.
Plugins that run on Node.js install again: the installer now checks the
Node.js major version rather than merely its presence, and names the version
it needs.
Plugin services start under a per-user installation again; they previously
failed before launch because of hardening directives a user-level service
manager is not allowed to apply.
aihummer settings finds the database address of the installation on its own,
as the other database commands already did.
An error the command already explained is no longer printed a second time as
raw text; the exit code is unchanged.
Command help is shown in the operator’s language and no longer carries
internal markers; status now shows an installation overview and the state of
optional services; doctor names a missing Node.js runtime and missing
fleet-registration material.
Security
Subscription limits can no longer be relaxed through the settings API: the two
vendor-managed keys are refused by the settings store itself, not by a single
request handler.
v1.0.15 (Core, stable) — 2026-08-01
Changed
Connector packages are now built reproducibly: the same source always yields a
byte-identical archive, so the published checksum can be independently
verified. Bundled connectors move to 1.0.1 as a result.
Fixed
A built-in plugin whose first deployment was interrupted by a gateway restart
no longer stays stuck forever; the next start picks it up and finishes the
install.
The instance now lists which agent tools it registered at startup, and names
the setting that enables each missing optional one, so a “that tool isn’t
available” answer can be diagnosed.
A single failed catalog refresh right after boot is reported calmly instead of
as a warning; only repeated failures are raised.
The message box in Sessions grows with the text again, up to a fixed height.
Plugin status badges are styled consistently with the type and built-in badges
next to them.
v1.0.14 (Core, stable) — 2026-07-31
New
Web search and the anti-detect browser now ship inside every build and are
installed offline, so both work out of the box with no setup step and no
download on the server.
Changed
Vendor-managed settings (web search, browser and the built-in memory service)
are no longer shown as instance options; the memory service keeps its update
action.
Fixed
A built-in plugin whose very first deployment failed on a new cloud server is
now retried automatically instead of staying broken.
A catalog refresh can no longer replace a signed plugin entry with an unsigned
one, which had made several first-party plugins refuse to install.
Failure to load the model list now names its actual cause instead of a generic
“temporarily unavailable”.
Suspending a subscription now really stops the assistant everywhere and the
reason is shown on every page of the administration interface.
Deleting a self-hosted server from the personal cabinet now removes it
completely, and only when the paid period has ended.
The message box in Sessions grows with the text, cloud plan names are
localized, and plugin badges no longer break their row.
v1.0.14-beta1 (Core, beta) — 2026-07-30
Security
Interrupted release publication can now be recovered only from the exact
reviewed source after the signed archive and current channel state pass
fail-closed integrity checks.
v1.0.13 (Core, stable) — 2026-07-29
Security
Production runtime credentials are no longer compiled into the release binary,
and the fleet bootstrap credential has moved out of release artifacts.
Privileged installation and release publishing now pin every dependency they
fetch: bundles carry a signed manifest binding version, platform and flavor,
and validly signed replay or substitution is rejected before anything is
written.
The compromised community signing root has been retired; third-party local
plugin execution now fails closed.
The published MCP endpoint, agent-authored schedules, event-stream sessions
and OpenAPI redirects each gained an explicit authorization and idempotency
boundary.
Managed Avito webhooks now use a per-installation secret path token kept in
the encrypted vault, and an upgrade migration strips the secret from plaintext
configuration.
Changed
The administrator UI toolchain moved to TypeScript 7 across the whole
workspace, with the browser used by the design-system audit pinned to the
matching Playwright revision.
Fixed
Customer contact details are now a read-only projection of the bound customer,
removing a writer that could diverge from billing.
Continuous-integration reliability fixes: build caches are no longer shared
between concurrent repositories, the web gate no longer needs an ambient Go
installation, and trust pins survive squash merges.
v1.0.12 (Core, stable) — 2026-07-27
Fixed
The gateway no longer refuses to start on a host without Caddy. In 1.0.11 the
unit required /etc/caddy/aihummer.d; when Caddy was absent systemd would not
run the service at all (226/NAMESPACE), leaving clean installs and cloud
provisioning without a working gateway. The path is now optional, and the
installer creates the directory where Caddy is actually present.
Community plugin units no longer break when they declare a directory that does
not exist yet — the same failure mode is fixed there too.
v1.0.11 (Core, stable) — 2026-07-27
Security
A custom cloud domain is reported as connected only after the exact instance
command succeeds and the public endpoint answers over a hostname-valid trusted
HTTPS certificate.
Fixed
Self-hosted instances now report a domain changed at runtime without requiring
a Core restart.
The built-in Einstein fallback now installs the released signed portable build
instead of an obsolete unavailable artifact.
Redirected non-interactive installer logs retain all earlier verification
output and no longer contain sparse NUL gaps.
v1.0.10 (Core, stable) — 2026-07-27
New
The administrator interface is now complete in 27 languages, with persistent
language selection and correct plural forms.
Security
Clean hosts can verify a release with stock OpenSSL before trusting or
downloading any additional verifier.
Agent delegation now keeps private memory and repeated tool calls scoped to
the acting agent, preventing one agent from reusing another agent’s data or
result.
Instance control replies now use an authenticated per-instance scope instead
of requesting a broad temporary queue.
Fixed
Plugin updates now preserve durable memory, cursors, local databases,
workspaces, output and generated credentials outside the replaceable
application files.
Provider model discovery now identifies live, cached, custom and unavailable
results honestly, while settings and first-party plugin forms expose only real
operator-editable values with the correct field types.
Managed-cloud owners can rotate an instance administrator password securely
from the customer portal without the plaintext appearing in status replies.
A fresh installation now connects to the AiHummer mobile app through the
released os-client plugin and returns the correct workspace during device
pairing.
Failed turns now show a safe localized reason, suggested next step and
diagnostic reference, preserve those details in Sessions, and offer retry only
when it is valid.
Browser and search tools become available only after real protocol readiness
checks; settings that could not yet be applied remain queued for a later
successful retry.
v1.0.9 (Core, stable) — 2026-07-27
New and improved
Lists, images and avatars show loading placeholders instead of appearing
frozen while data is requested.
In chat, Enter sends and Shift+Enter inserts a new line.
The current plan is shown with its localized, human-readable name.
Links to TikTok, Avito and VK use recognizable marks.
Fixed
Telegram and operating-system client services are found correctly after
installation.
Masked secret fields no longer confuse the displayed mask with the saved
secret value.
The page policy allows the configured Yandex Metrika connection without
weakening its other restrictions.
v1.0.8 (Core, stable) — 2026-07-26
New
VK and Avito connectors join Telegram as supported customer-channel
options.
An agent can be made available for self-management by the appropriate user,
within their granted workspace permissions.
Changed
Retired built-in browser channel options were removed. Test an agent in
Sessions, then connect one of the supported channel connectors.
[!NOTE]
This changelog tracks AiHummer Core. Plugins (Einstein, Bitrix24, SIP,
Pocket Agent) and the mobile/desktop app ship on their own version numbers.
New
First public stable line. Core reached its stable channel (v1.0.1) with
the community plugin marketplace; installs via install.sh.
Branded provider connect screens. Native connect screens (with logos) for
Russian and international model providers — YandexGPT, GigaChat, Cloud.ru, MTS AI,
OpenAI, Anthropic, Google, DeepSeek, xAI, Mistral, Groq and more; providers behind
a regional block are reachable through an outbound proxy (v1.0.4).
Real model lists in the add-provider dialog, with Russian providers ranked
first; the installer provisions Node.js for runtime:node plugins (v1.0.5).
Changed / fixed
Community plugins the author unpublishes drop from an instance’s store on the next
catalog sync (v1.0.2).
Plugins must declare the hosts/channels they use, enforced at install; the public
changelog is published in Russian too; provisioned cloud instances bind reliably and
report their real public IP; fixed first-login with emailed admin credentials and
immediate Telegram inbound (v1.0.3–v1.0.4).
Telegram poller clears stale webhooks and backs off; secrets are masked with their
real length; per-agent credential binding fixes; Codex multi-account support
(v1.0.5–v1.0.7).
v1.0.x — 2026-07-07
New
Personal account at my.aihummer.ru. Registration
with email confirmation, personal install links,
individual/company billing details with vendor confirmation, documents
(invoices and acts), consents and 27 UI languages. The public install script
is gone — installation now starts in the
portal.
Roles with configurable permissions. The “Roles” page: custom roles with
read/write checkboxes per resource domain; built-in roles (owner, admin,
operator, member) are read-only. See RBAC.
Vendor support from the personal account. Tickets and ideas to the vendor
(with attachments and message threads) are sent from your
personal account on my.aihummer.ru. The
“Support” and “Community” screens were removed from the web interface.
Visual orchestration. The “Graphs” page — a flowchart editor for
multi-agent workflows with JSON export/import. See
Orchestration.
Shared skills. A library of reusable skills with vendor “Out of the box”
presets. See Tools.
Channel bindings. The “Bindings” block on the “Channels” page assigns a
default agent to each channel. See Routing.
Sessions. New sessions straight from the admin UI, files in messages (the
model receives the extracted text), toggles for per-turn cost and tool
output.
Multi-account connections. Several accounts of one provider per user
(“+ account”), personal and workspace-shared connections. See
Connections.
Notifications. An event inbox plus a category × channel matrix delivering
to webui, email, Telegram and push.
Einstein is a built-in plugin. Memory installs automatically and cannot be
removed; settings live in the “Einstein (memory)” category.
Interface. Live logs with search and level filter, auto-refreshing pages,
paginated lists, hash navigation, dark/light theme and the mascot Ham.
Changed
CLI: the fleet and completion commands are removed; uninstall requires
root; settings list shows only user-facing keys. See the
CLI reference.
“Projects” are removed from the product.
v1.0.x — 2026-06-27
Added
MAX channel. Added support for the Russian messenger
MAX: the agent runs as a bot — it ingests inbound
messages, runs a turn and replies back, just like on Telegram. The connector
installs from the built-in
Marketplace and is configured in the Admin
UI.
Expanded personal-integration marketplace. Each user connects external
accounts to themselves as
zero-code integrations: Gmail, Google Calendar,
Google Contacts, Google Tasks, Google Drive, YouTube, Outlook Mail, Outlook
Calendar, OneDrive, Microsoft To Do, Todoist, Asana, Jira Cloud, ClickUp,
GitLab, Fitbit, Oura Ring, Spotify, Samsung SmartThings and more.
Two-mode plugin publishing. An extended
Plugin SDK (keygen, package, sign,
publish --private/--public) and a new
Publishing a plugin page: private side-load
into your instance (Admin UI / POST /v1/admin/modules/upload, trust store,
pinned key) and the public registry via a PR to marketplace-catalog
(auto-validator + AI review + manual merge + counter-signing). The manifest
gained store-page fields description / icon / screenshots and publisher
identity (publisher / visibility / publisher_key_id).
Multi-source catalog. Add extra sources in Plugins → Sources; the
community catalog of third-party plugins is added separately and never
overwrites the official one. AiHummer plugins carry an Official badge and
rank first; third-party ones sort by download count. Updates re-run the
signature check.
Improved
Refreshed documentation: a single bilingual navigation (RU/EN), in-docs search
(⌘K) and quick “Download the app” and “Open Swagger” cards in the sidebar.
v1.0 — baseline
The baseline capabilities of the v1.0 line, as a reference point for later
changes.
A finished product, not a framework. A single self-hosted service combines
the control-plane and the turn engine; a typical install is one service plus
PostgreSQL.
Host-native, no Docker. Deployed as a release tarball managed by systemd;
no containers or orchestrators.
Multi-agent orchestration with sub-agents and reasoning strategies
(plan-steps, reflect, debate, best-of-N, self-heal).
First-class agents with personas, a structured prompt and a per-agent
model.
Long-term memory (Einstein) — facts extracted as reviewable claims and
promoted to memory; recall is wrapped in a data-fence against prompt injection.
Knowledge / RAG with citations, plus deep_research for multi-step
reports.
Channels — Telegram, Bitrix24, SIP telephony and the mobile and desktop
app, extended by installable connectors in later releases.
OpenAI-compatible API — POST /v1/chat/completions with SSE streaming.
No mandatory paid models — runs on free/local models and a Codex/ChatGPT
subscription transport; per-tenant BYOK is optional.
Security as a baseline property — an encrypted credential vault, enterprise
SSO (SAML / LDAP / SCIM / OIDC), Postgres Row-Level Security for tenant
isolation, human-in-the-loop approval gates and audit.
A plugin marketplace with one-click, host-native install.
A history of notable AiHummer changes. The current line is **v1.0.x**. Each
entry below carries its date and the components it touched; the
[upgrade guide](/en/v1.0/operations/upgrade-policy) explains how to move up.
> [!NOTE]
> This page lists changes that matter to users and administrators. The exact
> build version is visible in the Admin UI and in the
> [API explorer (Swagger)](/api/).
## v1.0.17 (Core, stable) — 2026-08-02
**Fixed**
- Web search now really starts on a fresh install: its settings are written
before the readiness check and it gets a freshly generated secret key, so the
service no longer refuses to run with the default one.
- Node.js now ships inside the bundle and installs offline, so plugins that need
it — the AiHummer app, pocket-agent and the channel connectors — install on
distributions whose own Node.js is too old.
- A release no longer fails because a large download is merely slow: transfers
resume where they stopped and are aborted only when they actually stall.
**Changed**
- `aihummer status` now closes with next steps chosen for what it found: a
gateway that is down leads with its journal, a healthy one with diagnostics,
settings and the documentation. Only real commands are suggested.
## v1.0.16 (Core, stable) — 2026-08-02
**New**
- A knowledge source can now belong to one AI employee or be shared by all of
them, and retrieval respects that binding.
**Changed**
- The AiHummer app plugin moves to the published 1.0.4 release, which carries
the device sign-in fixes.
**Fixed**
- A fresh install no longer stops right after unpacking the bundled browser: an
optional sidecar can never abort the installation, so the gateway, the
database and every plugin are set up as intended.
- The bundled web search now starts on hosts with Python 3.12, and the bundled
browser gets the system libraries it needs; a missing library is reported
honestly instead of leaving the service in a restart loop.
- Plugins that run on Node.js install again: the installer now checks the
Node.js major version rather than merely its presence, and names the version
it needs.
- Plugin services start under a per-user installation again; they previously
failed before launch because of hardening directives a user-level service
manager is not allowed to apply.
- `aihummer settings` finds the database address of the installation on its own,
as the other database commands already did.
- An error the command already explained is no longer printed a second time as
raw text; the exit code is unchanged.
- Command help is shown in the operator's language and no longer carries
internal markers; `status` now shows an installation overview and the state of
optional services; `doctor` names a missing Node.js runtime and missing
fleet-registration material.
**Security**
- Subscription limits can no longer be relaxed through the settings API: the two
vendor-managed keys are refused by the settings store itself, not by a single
request handler.
## v1.0.15 (Core, stable) — 2026-08-01
**Changed**
- Connector packages are now built reproducibly: the same source always yields a
byte-identical archive, so the published checksum can be independently
verified. Bundled connectors move to 1.0.1 as a result.
**Fixed**
- A built-in plugin whose first deployment was interrupted by a gateway restart
no longer stays stuck forever; the next start picks it up and finishes the
install.
- The instance now lists which agent tools it registered at startup, and names
the setting that enables each missing optional one, so a "that tool isn't
available" answer can be diagnosed.
- A single failed catalog refresh right after boot is reported calmly instead of
as a warning; only repeated failures are raised.
- The message box in Sessions grows with the text again, up to a fixed height.
- Plugin status badges are styled consistently with the type and built-in badges
next to them.
## v1.0.14 (Core, stable) — 2026-07-31
**New**
- Web search and the anti-detect browser now ship inside every build and are
installed offline, so both work out of the box with no setup step and no
download on the server.
**Changed**
- Vendor-managed settings (web search, browser and the built-in memory service)
are no longer shown as instance options; the memory service keeps its update
action.
**Fixed**
- A built-in plugin whose very first deployment failed on a new cloud server is
now retried automatically instead of staying broken.
- A catalog refresh can no longer replace a signed plugin entry with an unsigned
one, which had made several first-party plugins refuse to install.
- Failure to load the model list now names its actual cause instead of a generic
"temporarily unavailable".
- Suspending a subscription now really stops the assistant everywhere and the
reason is shown on every page of the administration interface.
- Deleting a self-hosted server from the personal cabinet now removes it
completely, and only when the paid period has ended.
- The message box in Sessions grows with the text, cloud plan names are
localized, and plugin badges no longer break their row.
## v1.0.14-beta1 (Core, beta) — 2026-07-30
**Security**
- Interrupted release publication can now be recovered only from the exact
reviewed source after the signed archive and current channel state pass
fail-closed integrity checks.
## v1.0.13 (Core, stable) — 2026-07-29
**Security**
- Production runtime credentials are no longer compiled into the release binary,
and the fleet bootstrap credential has moved out of release artifacts.
- Privileged installation and release publishing now pin every dependency they
fetch: bundles carry a signed manifest binding version, platform and flavor,
and validly signed replay or substitution is rejected before anything is
written.
- The compromised community signing root has been retired; third-party local
plugin execution now fails closed.
- The published MCP endpoint, agent-authored schedules, event-stream sessions
and OpenAPI redirects each gained an explicit authorization and idempotency
boundary.
- Managed Avito webhooks now use a per-installation secret path token kept in
the encrypted vault, and an upgrade migration strips the secret from plaintext
configuration.
**Changed**
- The administrator UI toolchain moved to TypeScript 7 across the whole
workspace, with the browser used by the design-system audit pinned to the
matching Playwright revision.
**Fixed**
- Customer contact details are now a read-only projection of the bound customer,
removing a writer that could diverge from billing.
- Continuous-integration reliability fixes: build caches are no longer shared
between concurrent repositories, the web gate no longer needs an ambient Go
installation, and trust pins survive squash merges.
## v1.0.12 (Core, stable) — 2026-07-27
**Fixed**
- The gateway no longer refuses to start on a host without Caddy. In 1.0.11 the
unit required `/etc/caddy/aihummer.d`; when Caddy was absent systemd would not
run the service at all (226/NAMESPACE), leaving clean installs and cloud
provisioning without a working gateway. The path is now optional, and the
installer creates the directory where Caddy is actually present.
- Community plugin units no longer break when they declare a directory that does
not exist yet — the same failure mode is fixed there too.
## v1.0.11 (Core, stable) — 2026-07-27
**Security**
- A custom cloud domain is reported as connected only after the exact instance
command succeeds and the public endpoint answers over a hostname-valid trusted
HTTPS certificate.
**Fixed**
- Self-hosted instances now report a domain changed at runtime without requiring
a Core restart.
- The built-in Einstein fallback now installs the released signed portable build
instead of an obsolete unavailable artifact.
- Redirected non-interactive installer logs retain all earlier verification
output and no longer contain sparse NUL gaps.
## v1.0.10 (Core, stable) — 2026-07-27
**New**
- The administrator interface is now complete in 27 languages, with persistent
language selection and correct plural forms.
**Security**
- Clean hosts can verify a release with stock OpenSSL before trusting or
downloading any additional verifier.
- Agent delegation now keeps private memory and repeated tool calls scoped to
the acting agent, preventing one agent from reusing another agent's data or
result.
- Instance control replies now use an authenticated per-instance scope instead
of requesting a broad temporary queue.
**Fixed**
- Plugin updates now preserve durable memory, cursors, local databases,
workspaces, output and generated credentials outside the replaceable
application files.
- Provider model discovery now identifies live, cached, custom and unavailable
results honestly, while settings and first-party plugin forms expose only real
operator-editable values with the correct field types.
- Managed-cloud owners can rotate an instance administrator password securely
from the customer portal without the plaintext appearing in status replies.
- A fresh installation now connects to the AiHummer mobile app through the
released os-client plugin and returns the correct workspace during device
pairing.
- Failed turns now show a safe localized reason, suggested next step and
diagnostic reference, preserve those details in Sessions, and offer retry only
when it is valid.
- Browser and search tools become available only after real protocol readiness
checks; settings that could not yet be applied remain queued for a later
successful retry.
## v1.0.9 (Core, stable) — 2026-07-27
**New and improved**
- Lists, images and avatars show loading placeholders instead of appearing
frozen while data is requested.
- In chat, **Enter** sends and **Shift+Enter** inserts a new line.
- The current plan is shown with its localized, human-readable name.
- Links to TikTok, Avito and VK use recognizable marks.
**Fixed**
- Telegram and operating-system client services are found correctly after
installation.
- Masked secret fields no longer confuse the displayed mask with the saved
secret value.
- The page policy allows the configured Yandex Metrika connection without
weakening its other restrictions.
## v1.0.8 (Core, stable) — 2026-07-26
**New**
- **VK and Avito connectors** join Telegram as supported customer-channel
options.
- An agent can be made available for self-management by the appropriate user,
within their granted workspace permissions.
**Changed**
- Retired built-in browser channel options were removed. Test an agent in
**Sessions**, then connect one of the supported channel connectors.
## v1.0.1–v1.0.7 (Core, stable) — 2026-07-13 … 2026-07-22
> [!NOTE]
> This changelog tracks **AiHummer Core**. Plugins (Einstein, Bitrix24, SIP,
> Pocket Agent) and the mobile/desktop app ship on their own version numbers.
**New**
- **First public stable line.** Core reached its **stable** channel (v1.0.1) with
the community plugin marketplace; installs via `install.sh`.
- **Branded provider connect screens.** Native connect screens (with logos) for
Russian and international model providers — YandexGPT, GigaChat, Cloud.ru, MTS AI,
OpenAI, Anthropic, Google, DeepSeek, xAI, Mistral, Groq and more; providers behind
a regional block are reachable through an outbound proxy (v1.0.4).
- **Real model lists in the add-provider dialog**, with Russian providers ranked
first; the installer provisions Node.js for `runtime:node` plugins (v1.0.5).
**Changed / fixed**
- Community plugins the author unpublishes drop from an instance's store on the next
catalog sync (v1.0.2).
- Plugins must declare the hosts/channels they use, enforced at install; the public
changelog is published in Russian too; provisioned cloud instances bind reliably and
report their real public IP; fixed first-login with emailed admin credentials and
immediate Telegram inbound (v1.0.3–v1.0.4).
- Telegram poller clears stale webhooks and backs off; secrets are masked with their
real length; per-agent credential binding fixes; Codex multi-account support
(v1.0.5–v1.0.7).
## v1.0.x — 2026-07-07
**New**
- **Personal account at [my.aihummer.ru](https://my.aihummer.ru).** Registration
with email confirmation, [personal install links](/en/v1.0/getting-started/installation),
individual/company billing details with vendor confirmation, documents
(invoices and acts), consents and 27 UI languages. The public install script
is gone — installation now starts in the
[portal](/en/v1.0/commercial/personal-account).
- **Roles with configurable permissions.** The "Roles" page: custom roles with
read/write checkboxes per resource domain; built-in roles (owner, admin,
operator, member) are read-only. See [RBAC](/en/v1.0/security/rbac).
- **Vendor support from the personal account.** Tickets and ideas to the vendor
(with attachments and message threads) are sent from your
[personal account](/en/v1.0/commercial/personal-account) on my.aihummer.ru. The
"Support" and "Community" screens were removed from the web interface.
- **Visual orchestration.** The "Graphs" page — a flowchart editor for
multi-agent workflows with JSON export/import. See
[Orchestration](/en/v1.0/concepts/orchestration-subagents).
- **Shared skills.** A library of reusable skills with vendor "Out of the box"
presets. See [Tools](/en/v1.0/concepts/tools).
- **Channel bindings.** The "Bindings" block on the "Channels" page assigns a
default agent to each channel. See [Routing](/en/v1.0/concepts/routing).
- **Sessions.** New sessions straight from the admin UI, files in messages (the
model receives the extracted text), toggles for per-turn cost and tool
output.
- **Multi-account connections.** Several accounts of one provider per user
("+ account"), personal and workspace-shared connections. See
[Connections](/en/v1.0/access/connections-oauth2).
- **Notifications.** An event inbox plus a category × channel matrix delivering
to webui, email, Telegram and push.
- **Einstein is a built-in plugin.** Memory installs automatically and cannot be
removed; settings live in the "Einstein (memory)" category.
- **Interface.** Live logs with search and level filter, auto-refreshing pages,
paginated lists, hash navigation, dark/light theme and the mascot Ham.
**Changed**
- CLI: the `fleet` and `completion` commands are removed; `uninstall` requires
root; `settings list` shows only user-facing keys. See the
[CLI reference](/en/v1.0/reference/cli).
- "Projects" are removed from the product.
## v1.0.x — 2026-06-27
**Added**
- **MAX channel.** Added support for the Russian messenger
[MAX](/en/v1.0/channels/max): the agent runs as a bot — it ingests inbound
messages, runs a turn and replies back, just like on Telegram. The connector
installs from the built-in
[Marketplace](/en/v1.0/marketplace/overview-tiers) and is configured in the Admin
UI.
- **Expanded personal-integration marketplace.** Each user connects external
accounts to themselves as
[zero-code integrations](/en/v1.0/marketplace/zero-code): Gmail, Google Calendar,
Google Contacts, Google Tasks, Google Drive, YouTube, Outlook Mail, Outlook
Calendar, OneDrive, Microsoft To Do, Todoist, Asana, Jira Cloud, ClickUp,
GitLab, Fitbit, Oura Ring, Spotify, Samsung SmartThings and more.
- **API explorer (Swagger).** A new interactive
[API explorer (Swagger)](/api/) for the AiHummer endpoints — with built-in
authorization and a "Try it out" mode. See also
[Swagger in the API section](/en/v1.0/api/swagger).
- **Two-mode plugin publishing.** An extended
[Plugin SDK](/en/v1.0/marketplace/sdk) (`keygen`, `package`, `sign`,
`publish --private/--public`) and a new
[Publishing a plugin](/en/v1.0/marketplace/publishing) page: private side-load
into your instance (Admin UI / `POST /v1/admin/modules/upload`, trust store,
pinned key) and the public registry via a PR to `marketplace-catalog`
(auto-validator + AI review + manual merge + counter-signing). The manifest
gained store-page fields `description` / `icon` / `screenshots` and publisher
identity (`publisher` / `visibility` / `publisher_key_id`).
- **Multi-source catalog.** Add extra sources in **Plugins → Sources**; the
community catalog of third-party plugins is added separately and never
overwrites the official one. AiHummer plugins carry an **Official** badge and
rank first; third-party ones sort by download count. Updates re-run the
signature check.
**Improved**
- Refreshed documentation: a single bilingual navigation (RU/EN), in-docs search
(⌘K) and quick "Download the app" and "Open Swagger" cards in the sidebar.
## v1.0 — baseline
The baseline capabilities of the v1.0 line, as a reference point for later
changes.
- **A finished product, not a framework.** A single self-hosted service combines
the control-plane and the turn engine; a typical install is one service plus
PostgreSQL.
- **Host-native, no Docker.** Deployed as a release tarball managed by systemd;
no containers or orchestrators.
- **Multi-agent orchestration** with sub-agents and reasoning strategies
(plan-steps, reflect, debate, best-of-N, self-heal).
- **First-class agents** with personas, a structured prompt and a per-agent
model.
- **Long-term memory (Einstein)** — facts extracted as reviewable claims and
promoted to memory; recall is wrapped in a data-fence against prompt injection.
- **Knowledge / RAG** with citations, plus `deep_research` for multi-step
reports.
- **Channels** — Telegram, Bitrix24, SIP telephony and the mobile and desktop
app, extended by installable connectors in later releases.
- **OpenAI-compatible API** — `POST /v1/chat/completions` with SSE streaming.
- **No mandatory paid models** — runs on free/local models and a Codex/ChatGPT
subscription transport; per-tenant BYOK is optional.
- **Security as a baseline property** — an encrypted credential vault, enterprise
SSO (SAML / LDAP / SCIM / OIDC), Postgres Row-Level Security for tenant
isolation, human-in-the-loop approval gates and audit.
- **A plugin marketplace** with one-click, host-native install.
