Repository navigation
v0.7.0
Added
- agents: a container image for the admin UI, published to GHCR on every
push tomainasghcr.io/mindconnect-ai/mc-agent-admin-ui. It is a layered
Spring Boot image, so a new version is a ~3 MB application layer on top of an
unchanged dependency layer instead of a fresh 344 MB — which is what makes
redeploying onto a small VPS practical. Chromium ships in the image, so the
Playwright-backed browser tools work without downloading a browser at
runtime.deploy/holds a single-host Compose setup to run it behind Caddy,
which obtains and renews its TLS certificates itself, next to Postgres and
Keycloak.
Changed
-
agents: every id is a typed record —
AgentId,SessionId,
ConversationId,MessageId,ChatTurnId,ParticipantId,
ConversationSummaryId,TraceId,LlmConfigId,FileId,AgentToolId
and friends — instead of aUUIDor a bareString. Ports, services,
repositories, the tool SPI, the builder facade and the CLI client take these
types, so afindById(AgentId)refuses aSessionIdat compile time. Id
values are lower-case, file-name-safe strings: a readableweb-researcher
is as valid as a UUID. In JSON an id is still its plain string.
AgentToolno longer points back at its agent: theagentDefinitionId
field is gone,AgentTool.of(name, …)takes no agent id, and older agent
files that still carry the field load as before. -
agents: the namespace is no longer part of any domain object, id, port
or service, andAuthenticationInfocarries only the user and roles.
Persistence adapters are bound to one namespace when they are built, and a
process serves exactly one: the Spring starters readmindconnect.namespace
(defaultlocal;MC_NAMESPACEin the apps), the builder takes
namespace(...), and adapters take it as their last constructor argument.
Everything a namespace stores on disk sits in one directory,
<mindconnect.data.base-dir>/<namespace>/—data/local/by default, with
files,workflowsandvector-storesbeside the rest — so the properties
mindconnect.file-store.dir,mindconnect.workflow-admin.dirand
mindconnect.vector-store.dirare gone, and existing data has to move into
that directory (or start with an empty one).
On Postgres everymc_*table carries anamespacecolumn in its primary
key and the workflow tables apartition_key, and pgvector tables are named
vs_<namespace>__<store>; there is no migration, so drop themc_*tables
of an existing database before starting this version (existingvs_*
stores are not picked up either). The REST API loses itsnamespace
parameters — the query parameter of the agent endpoints and of
GET /api/sessions, and the field in the bodies ofPOST /api/agentsand
POST /api/sessions— agent, session and conversation JSON lose their
namespacefield,AgentDefinition.create(...)its namespace argument, and
the propertymindconnect.agent.stateless.namespaceis gone. -
agents: the protocol (
mc-agent-protocol) no longer names a tenant:
Sessions.open(agentName)andConversations.create()lose their
namespaceargument, andSessionandConversationtheirnamespace
field.AgentRuntimeBackendneeds none either — the runtime it wraps is
bound to one. -
agents:
NamespaceandAuthenticationInfomoved frommc-common
(packageai.mindconnect.common) into the new dependency-free module
mc-agent-domain, packageai.mindconnect.agent, together withUserId,
whichAuthenticationInfo.userId()now returns instead of aString.
Embedders repoint two imports and wrap the user id inUserId.of(...); the
agents modules pull the new module in transitively.
mc-commonis tenant-free again, which is what the workflow and taskqueue
areas expect from it; its unusedDomainEventrecord went with the move. -
agents: the runtime's packages moved one level down, from
ai.mindconnect.agent.{domain,port,service,memory,tools,adapter}to
ai.mindconnect.agent.runtime.{domain,port,service,memory,tools,adapter},
so thatai.mindconnect.agentitself is left to the shared vocabulary.
Unchanged: the tool SPIai.mindconnect.agent.tool, the tool modules
ai.mindconnect.agent.tools.*and the memory strategies
ai.mindconnect.agent.memory.strategy. In the same spirit the Postgres
file store moved fromai.mindconnect.filestore.pgto
ai.mindconnect.filestore.adapter.pg. Embedders repoint their imports;
logger names configured for the old packages (for example
ai.mindconnect.agent.service) need theruntimesegment too. -
agents: the bundled agents default to OpenAI instead of a local LM
Studio server.agent-default, the LLM config every shipped agent
references, is now an alias that delegates toopenai-default, so a fresh
install works as soon asOPENAI_API_KEYis set — which is what most
people have — instead of requiring a 120B model onlocalhost:1234.
url-readerfollows suit and no longer needs the localgemma-reader
model. Repointing the alias (inagent-default.jsonor the Admin UI)
moves every bundled agent to another provider at once;lm-studio-default
still carries the previous local settings. Existing installations are not
changed behind your back: a storedagent-defaultthat differs from the
seed shows up as a pending migration in the Admin UI, and the CLI logs the
difference and keeps what it has.
Fixed
-
agents: a store file of the
memoryvector-store backend loads whatever
its formatting. It is written one chunk per line, and it was read that way
too, so a file someone had pretty-printed to read it counted as unreadable —
and the chat's attachment list then showed no chunks without saying why. The
file is now read as a sequence of JSON objects, and an unreadable session
store is logged as a warning. -
agents: a tool call no longer fails now and then with "tool call was
interrupted before completion: tool task ended FAILED without a result".
With the file persistence, a session was saved by truncating and rewriting
session.json; a tool task reading the session at that moment found an
empty file and failed before the tool ran. Sessions are now written to a
temporary file and moved into place in one step. -
agents: a sub-agent's approval question is answered only through the
chat that shows its card. The open questions were keyed by the tool call's
id alone, which the model provider hands out and which is unique only within
one response: an answer sent through another session reached the waiting
tool all the same, and two chats that got the same call id shared one entry,
so one card never appeared.POST /api/sessions/{id}/approvals/{callId}now
answers 404 when that session has no such open question. -
agents: the admin UI's Logout button no longer ends with "The backend is
unreachable". The header's logout is a link, and the SPA router turned every
such click into a fetch — but logout answers with a redirect to Keycloak on
another host, which a fetch cannot follow. The session was destroyed all the
same, so it logged you out and showed an error while doing it. Logout is now
an ordinary page navigation. -
agents: a tool provider that cannot say whether it is ready no longer
takes the catalogue with it.isAvailable()became a per-lookup call when
provider binding moved off the startup path; a provider throwing there would
have failed every turn and every catalogue render, for every provider. It is
now caught and logged, and the bundle counts as unavailable. The
documentation for tool authors says whatbindandisAvailablemay expect
of their surroundings — both run more often, and in more places, than they
used to. -
agents: the Spring runtime starts the tool warm-up once its context is
refreshed rather than while the registry is being built. Binding asks the
environment for services, and that environment resolves them from the
application context: doing it from a warm-up thread mid-refresh meant
queueing behind the very startup that was waiting for the first round, so a
provider that should have been ready in microseconds could miss its window
for no reason.SpiToolRegistry.deferred(...)is the registry without the
warm-up for a host that starts in phases; embedders that build it directly
are unaffected.
Changed
- agents: resolving tools no longer holds up the start. Providers that
reach outside the process — the Gmail tools spawn an MCP server in a
container — used to bind on the startup thread, so a machine without a
container runtime paid the full initialization timeout before the
application served its first request; here that was 47 seconds against 2.
Every provider now binds on its own virtual thread, the first round gets a
short grace period so in-process providers are ready when the runtime is,
and anything slower joins the catalog the moment it is ready. A provider
that fails for a passing reason is tried again a few times over about a
minute, which means a container runtime started after the application no
longer needs a restart to be noticed.SpiToolRegistryisAutoCloseable;
closing it stops the warm-up.
Fixed
-
agents: an MCP server whose command cannot be run says so at once
instead of holding the application back. The Gmail tools spawn their server
through docker; on a machine without it — or with a docker link left behind
by an uninstalled Docker Desktop — startup used to stall for the full
initialization timeout and log a dropped reactive error before deciding the
provider was unavailable. The proxy now checks that the command resolves to
something executable before spawning, and names it when it does not. -
agents: a transcription job asked to wait no longer answers with a
server error.GET /api/transcriptions/{id}?wait=treats running out of
seconds as what it is — the job is still going — and answers with the job as
it stands. The transcription call itself now has a deadline of its own, so
an endpoint that accepts a connection and then goes quiet can no longer hold
a queue worker and leave a job running for ever. And an endpoint that
rejects thestreamfield, which is asked for whenever a caller listens for
deltas, is simply asked again without it rather than failing the job; a
config that would rather skip that round trip sets the provider parameter
stream=off.
What's Changed
- Four fixes the whisper review found, just after 0.6.0 by @beisdog in #54
- Tool providers warm up in the background by @beisdog in #55
- An AGENTS.md a coding agent can afford to read by @beisdog in #56
- Review fixes for the background warm-up by @beisdog in #57
- Ship the admin UI as a container image by @beisdog in #58
- Move the runtime packages under ai.mindconnect.agent.runtime; default the bundled agents to OpenAI by @beisdog in #60
- Move Namespace and AuthenticationInfo into a shared mc-agent-domain module by @beisdog in #59
- Typed ids without namespace; stores bound to one namespace by @beisdog in #61
Full Changelog: v0.6.0...v0.7.0