v0.1.1

What's Changed

• Fix HITL approval recovery by @SemiGlassFace in #3
• feat: copy button on code blocks + pin packageManager by @jfilipiuk in #6
• feat: render mermaid fences as diagrams with click-to-zoom by @jfilipiuk in #7

New Contributors

• @SemiGlassFace made their first contribution in #3
• @jfilipiuk made their first contribution in #6

Full Changelog: v0.1.0...v0.1.1

v0.1.0

EvoScientist WebUI v0.1.0 — No More Ghost Agents 👻

G'Day! v0.1.0 kicks off the stable 0.1 line — 0.0.9 took the WebUI out of beta, and this release makes it official in the version number. It's a focused reliability release that keeps the Agents board honest after a backend restart. EvoScientist v0.1.6 (#279) made conversations survive EvoSci deploy restarts — great news, but it exposed a latent gap in the WebUI: background tasks from before a restart could show as perpetually Running with a forever-ticking timer. This release introduces a proper Expired state, stops redundant polling, and hardens the side-chat error path.

---

👻 Expired — ghost "Running" tasks are gone

When the backend restarts, your conversations come back — but the background sub-agent threads (writing / data analysis) do not. The board used to fall back to the cached task status, which is stuck on running forever.

• Evidence-based detection — when the task's run provably no longer exists (the backend answers 404), the task is marked Expired: gray dot, no pulse, no made-up duration.
• Honest expanded view — expanding an expired task shows a short note ("this task ran before a backend restart; its records are gone — files it produced are still in the workspace") instead of an empty steps list, with the Notify / follow-up controls hidden (they couldn't work anyway).
• Never auto-reported — expired tasks are excluded from auto-report and the "Notify main chat" button, so the main agent is never poked about a task it can no longer look up.
• Transient failures stay transient — a network blip or a briefly-unreachable backend still falls back to the cached status as before; only a definitive 404 produces Expired.

---

🔇 Quieter polling

• 404s are remembered — once a task's run has 404'd, the verdict is permanent for that run, so the board stops re-requesting it every 3 seconds. Switching conversations or backends re-probes fresh.

---

🛠 Side-chat ("Direct follow-up") hardening

• No more vanishing steps — if a follow-up run came back without a transcript (a server-side error path), the panel used to overwrite the agent's loaded steps with an empty Steps (0) that stuck. It now keeps the existing steps and your draft, and shows an error line instead.
• Clearer errors — the message now distinguishes "the agent hit an error processing this follow-up" from "couldn't reach this agent".

---

📦 Updating

Nothing to do — npx @evoscientist/webui@latest (and EvoScientist's WebUI mode) always pulls the latest version. Just restart the UI. Pairs best with EvoScientist v0.1.6+ (session persistence).

Full Changelog: v0.0.9...v0.1.0

v0.0.9

EvoScientist WebUI v0.0.9 — Out of Beta 🎉

G'Day! v0.0.9 is a small but meaningful milestone: the WebUI is officially out of beta. After the feature lines that landed across 0.0.5–0.0.8 — the workspace browser, skills marketplace, memory editor, background-agent board with two-way communication, and compaction handling — the interface is now stable enough for everyday research use, so the BETA badge is retired. This release also ships clearer deployment-configuration copy to pave the way for connecting to public deployments.

---

🎓 Out of Beta

The static BETA tag next to the EvoScientist title in the header is gone.

• Why now — the core surface (chat + streaming, human-in-the-loop approvals, workspace files, skills, memory, background agents) has been exercised and hardened over the past releases; the product is ready for regular use.
• What changed — the badge component was removed entirely; the header now shows just the EvoScientist wordmark.

---

⚙️ Clearer Deployment Configuration

The Configuration dialog now explains exactly what the Deployment URL is and where it comes from.

• Auto-detected by default — the copy makes clear that your local deployment (from EvoSci deploy) is detected and prefilled automatically, so in the common case you just hit Save.
• Public deployments — the field can also point at a public deployment URL, groundwork for upcoming remote-deployment support.

---

📦 Updating

Nothing to do — npx @evoscientist/webui@latest (and EvoScientist's WebUI mode) always pulls the latest version. Just restart the UI.

Full Changelog: v0.0.8...v0.0.9

v0.0.8

EvoScientist-WebUI v0.0.8

Full Changelog: v0.0.7...v0.0.8

v0.0.7

EvoScientist-WebUI v0.0.7

Full Changelog: v0.0.6...v0.0.7

v0.0.6

EvoScientist-WebUI v0.0.6

Full Changelog: v0.0.5...v0.0.6

v0.0.5

EvoScientist-WebUI v0.0.5

Full Changelog: v0.0.4...v0.0.5

v0.0.4

EvoScientist-WebUI v0.0.4

Full Changelog: v0.0.2...v0.0.4

v0.0.2

EvoScientist WebUI Initial Version