You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A server's tool can run as a background job. An MCP server marks a
tool _meta: {"mecha-factory.ai/background": true} in its tool list, and a
call to it answers "being made" at once and runs past the turn as the
chat's job — queued, reorderable and stoppable, like a picture — with the
result landing on the same row when it is done. The call carries the chat's
folder as an absolute path (_meta["mecha-factory.ai/workspace"]) for the
server to write into, and a result whose first line is video: <path>.mp4, the path relative to that folder, plays under its row,
once per clip. Stop sends the server notifications/cancelled, a job
is bounded at two hours, and a job a restart of mecha serve left running
is settled as not made rather than left with a dead Stop. Only the server
can opt a tool in; no setting does, and a tool that sends to a recipient
the model names is never deferred.
Persona chats can be given a server's tools.[[mcp]] personas = true —
global config only, off by default — is your statement that the server reads
none of your private stores. Each persona still lists the tools it may use,
and a persona chat still refuses a tool that is not read-only — an MCP tool
is read-only only where its server declares readOnlyHint — or that sends
to a recipient the model names. A persona's background call names its
folder, its library character and its voice-library voice in _meta["mecha-factory.ai/persona"], so a server that makes sound can use
the persona's voice; never its prompt, display name or anything it said.
While such a job runs the chat says "working on it…", and the call screen
says so beside a picture being drawn. No server's background job reaches an
incognito chat.
Changed
argon2 0.6 and rusqlite 0.40. A library lock set before the upgrade
still opens; a new lock's salt comes from argon2 itself. A dashboard query
whose timeout or read-only authorizer cannot be installed is now refused
rather than run without it.
Fixed
Switching on mail, documents or the graph finishes wiring them. mecha features enable mail (and docs, graph) wrote only the switch,
so the feature still read off with "add an [[mcp]] entry" — and mecha setup's yes to mail stopped there instead of opening the sign-in. It now
writes the [[mcp]] entry the docs give where none runs the program,
with its results read as untrusted and the program by its absolute path;
mail's sends, replies and calendar changes and documents' writes are
staged in the outbox when you have no [outbox] table yet, unless a [[rule]] of yours names one of them. An [outbox] you wrote is never
edited: enable names the routing it lacks. A program that is not installed
is named with its install command.
Voice recording and cloning work after mecha features enable voice.
The installed speech server reads voices from ~/.mecha/sidecars/speech/voices, but nothing named that directory in [voice] voices_dir, so recording a voice said "not configured" after a
complete install. The install now writes it where there is no [voice]
table, says the line to add to one you wrote, and warns when the one named
differs from what the server reads. The "not configured" message names the
installed path.