[4.0.6] - 2026-11-16
Added
parlant lintlints a Parlant agent project through your coding agent. It
prints instructions for the coding agent: which lint chapters to run, each in
its own subagent (parlant lint --section SECTION --chapter CHAPTERprints a
chapter's rules), and how to handle findings by severity. HIGH findings are
fixed right away, at most 3 MEDIUM issue types are proposed per round, and
LOW ones only with your OK. The first sections are Behavior (observations
that combine several situations, whether alternatives or ones that must all
hold) and Wording and Tone of Voice (canned
responses rather than wording in policies or instructions). Every rule has an
ID, such asBHV001, that stays the same across releases.parlant initnow installs a git pre-push hook (.githooks/pre-push, set
throughcore.hooksPath) that stops a push until the commit has been linted,
and the scaffolded AGENTS.md tells the coding agent to runparlant lint
before every push. After linting and committing the fixes,parlant lint --donerecords the commit so the push goes through;git push --no-verify
skips the hook. A clone of the project turns the hook on with
git config core.hooksPath .githooks.--no-gitinstalls no hook.parlant dashboard agent cards AGENT_ID DESTINATIONwrites every file your
site serves so personal AI agents find your agent, intoDESTINATION/.well-known:
agent-card.jsonfor A2A, andpoppy.jsonandpoppy-0.4.jsonfor Poppy, the
Personal Agent Protocol that Meta Muse and Shopify use.--no-a2aand
--no-poppyleave a family out. The Poppy documents need the agent's site set
in the Dashboard, since Poppy identifies a business by its domain; without it the
command writes the card and says so.parlant dashboard agent viewshows the
agent's POPPY ADDRESS, andparlant widget initpoints at the new command.
parlant dashboard agent cardstill prints the A2A card alone for older
instructions.- The chat widget's
onPathChanged(path, notifyAgent)tells the agent which page
the visitor is on. It's called when the widget loads and when the path changes
without a reload;notifyAgent(path, data?)adds a custom event
({ type: "page_view", page: path, ...data }, sourcecustomer_ui) that doesn't start
a reply. A new conversation gets it before anything else, so the agent can tell
a question asked on your pricing page from one asked on your home page.
Changed
- At high agent effort, pruning previously discovered rules now defaults to
low model reasoning, matching rule ranking. Explicit model-route reasoning
settings still take precedence. - When one policy entails another, the entailed policy is now judged with the
policies that entail it in view. This helps when its wording relies on
theirs, such as "the add-on" that another policy defines. It still matches on
its own merits, and entailment works as before: when an entailing policy
matches, the entailed one is activated too. - Guests and signed-in customers may add custom events to their own sessions,
with sourcecustomer_ui, up to 4 KB of data and 30 a minute. Until now only
the backend could, so a site had to relay page views through its own server
with the admin key. Other sources still need the admin key; a custom permission
gate that doesn't grantCREATE_CUSTOM_EVENTkeeps refusing them.
PARLANT_CUSTOMER_UI_EVENT_MAX_BYTESchanges the size limit (4096 by default). - A chat widget with a video avatar now moves the video into a circle beside
the agent's name once the conversation scrolls, and the space it leaves
closes up. Scrolling up past the top brings it back. The header keeps its
height and fades out over the messages below the circle. The name and
subtitle fade out while the video moves and back in beside the circle, the
subtitle under the name. A photo avatar is now the same size as the docked
circle, and its header fades out over the messages below it too. Scrolling up
in the widget no longer gets pulled back down in a short conversation, and
sending a message brings the view to it.
On phones the widget only shows the circle, which is cropped onto the face
by the avatar'slaunchersetting. Your project keeps the copy
parlant widget initmade. To pick this up, run
parlant widget init --force, which replaces that copy and any changes you
made to it. - With Gemini as your provider, replies at medium, high and max effort and both
review checks now run on Gemini 4 Hydrogen instead of Gemini 3.8 Flash. Medium
effort keeps low reasoning. On a website agent this cut replies from 15–30
seconds to 6–8, and Hydrogen kept its reasoning out of replies where 3.8 Flash
at low reasoning had written it into one. Minimal and low effort stay on
Flash-Lite. Areactorreview.*route you set yourself is unchanged. To
keep the old model, route it explicitly, e.g.
"react": p.ModelConfig("gemini:gemini-3.8-flash", reasoning="low"). - LiteLLM's default for both review checks is now
gemini/gemini-4-hydrogen
instead ofgemini/gemini-3.8-flash.
Fixed
- An observation with a title but no note no longer appears in the agent's
instructions as an empty entry (its title followed by "Details: [None]",
without its condition). A rule now reaches the agent's prompt only when it
says something: its content (an observation's note, a policy's action), or
the tools it makes relevant, in which case its condition is shown even when
it has a title. Rules without content are also left out of the note that
tells the agent which instructions lost priority this turn. Observations
without a note keep working for relationships, canned-response scoping and
matching; they simply cost no prompt tokens. - Logging scopes now unwind after exceptions and cancellation, so later logs
in the same task do not retain stale component labels. - The chat widget centers its disclaimer and "Powered by Parlant" under the input on phones.
- The chat widget no longer shows "↓ New messages" in an empty or short chat that the
visitor scrolled up in. The pill now appears only when there is something below to jump to. - The chat widget no longer ends a finished reply with a stray
*. A reply with
an odd number of*bullets used to get one after its last word. Half-typed
bold and italics still close while a reply streams. To pick up this and the
other widget fixes, runparlant widget init --force, which replaces your
project's copy of the widget and any changes you made to it. - A reasoning level set on a Gemini 4 model in a schematic route, such as
"review.*": p.ModelConfig("gemini:gemini-4-hydrogen", reasoning="high"), is now
sent to Gemini. It used to be dropped, so the model thought at its own default. - Canned-response relevance now considers matches from every query chunk before
selecting the closest responses, retaining each response's best matching score.