Changelog

All notable changes to EasyCC are documented here. Written for humans, not machines.

[0.9.0-beta.6] Fewer interruptions, and a faster app

EasyCC asks for your approval far less often. Claude now handles everyday steps, like reading and editing files in your agent, without stopping to check with you each time. It still asks before anything risky or unusual. Looking things up with EasyCC's own tools, like File History or what's in a spreadsheet, never asks at all.

Scheduling goes through Scheduled. Ask Claude to do something every Monday or to remind you tomorrow, and it points you to Scheduled in Command Center, where the task sits with everything else you've scheduled. Before, Claude sometimes set up a schedule of its own that you couldn't see and that stopped when the conversation ended.

The app should feel faster, especially with a busy synced folder like OneDrive added, and in long conversations. EasyCC no longer reloads your whole file panel whenever something changes in an added folder, and long conversations no longer redraw every earlier message while Claude is typing.

Folders you chose to Skip for now are no longer saved to File History when their files change. Folders you've chosen to read work the same as before.

Behind the scenes

EasyCC now comes with a specific, tested version of Claude Code instead of whatever is newest on the day it's built. It also notes slow steps in its log, so freezes are easier to track down.

[0.9.0-beta.5] — Your files save where you can find them

Files now save into your agent folder, where you can see them in the file panel and open them like anything else. Some of the time, work was going somewhere else instead — a temporary folder on your computer that EasyCC doesn't show you and that gets cleared out on its own. The file was written, EasyCC said it was done, and there was no obvious way to find it.

This showed up most when you dragged in a document from outside your agent — from your Downloads folder, say — and asked for a change. What you were handed back was a working copy tucked away where you'd never look, while the document you dragged in sat unchanged. Now the updated version is saved into your agent folder under its own name, and EasyCC tells you that's where it went.

Behind the scenes

The underlying cause was that a conversation was never told which folder it was working in, so when it needed to write somewhere it fell back to whatever location it could name — usually a temporary one. Conversations are now told their agent folder up front, along with any other folders you've added through the file panel, and they're told plainly that finished work belongs there and never in a temporary folder. The same rule now applies to skills, which produce reports and exports of their own.

[0.9.0-beta.4] — Asana, and connectors that need their own setup

Asana is now in the connector library, alongside GitHub, Linear, and the rest. Asana asks you to set up an app on their website first — EasyCC walks you through it and shows you exactly what to paste where. It's a couple of minutes, and you only do it once.

That work opened up connectors that need their own setup in general. Some services won't set themselves up automatically the way most do, and EasyCC previously had no way to finish connecting to them — it asked for a detail it gave you nowhere to enter. Now it asks for what's needed up front, and you can change those details later from Settings → Connectors instead of removing the connector and starting again.

Connector windows also scroll properly now. On a shorter screen, the longer setup forms used to push the buttons off the bottom where you couldn't reach them.

Behind the scenes

Sign-in details are now tied to the service that issued them, so if a connector moves to a different sign-in service EasyCC stops rather than sending your details somewhere they don't belong. Client secrets go to your computer's password vault and are never written to a settings file or shown back on screen.

EasyCC also reads a connector's sign-in details from exactly the address the connector points at, rather than guessing from the website's home address — some services publish different details at each, and guessing led to sign-ins that couldn't finish.

A round of security housekeeping cleared the outstanding advisories in the app's building blocks, including one in the PDF reader that could have let a specially crafted PDF run code when you opened it.

[0.9.0-beta.3] — Slide decks, and checking the work

EasyCC can now edit PowerPoint decks. Ask it to change a name, a date, or a phrase across your slides and it makes the change in place — in the slides, the speaker notes, and any comments. It also checks its own work now: it re-opens the file and reads it back before telling you it's done, instead of assuming it worked.

Adding a large folder no longer quietly takes over your computer. Reading a folder means opening every Word, Excel, PowerPoint, and PDF file in it so you can search them and ask questions about them — and on a folder with hundreds of files, that takes a while. EasyCC now asks first. Choose Read them, or Skip for now and change your mind later by right-clicking the folder and choosing Read these files. Even if you skip, you can still ask for a single document by name whenever you need it.

Folders you add are watched right away. Change one of those files in Word or Excel and it shows up in EasyCC immediately, and the change is saved to File History. Before, you had to close and reopen your agent first, and anything you changed in the meantime went unrecorded.

Two folders whose names start the same — Reports and Reports Archive, say — no longer get confused with each other. Files in the second one open normally instead of showing an error.

Behind the scenes

Claude is now required to confirm a file is intact before saying that it is, and can no longer assemble Word, Excel, or PowerPoint files by hand — that was behind decks that looked finished but wouldn't open. Folders you add are also no longer searched through the bulky support folders some projects carry, and a round of security housekeeping cleared the outstanding advisories in the app's building blocks.

[0.9.0-beta.2] — EasyCC comes to Mac

EasyCC now runs on Mac — and just like on Windows, everything's built in. Pick the download for your Mac (Apple silicon or Intel chip), drag it to Applications, and you're working. Claude Code comes bundled inside the app, so there's nothing else to install first.

Updating EasyCC is clearer too. When a new version is ready, there's now one obvious Update now button — in the notification, in Settings, and in the menu under your profile picture. Click it and EasyCC downloads the update, restarts, and picks up right where you left off. Prefer to wait? "Update when I quit EasyCC" and "Remind me tomorrow" are still there.

Getting started is quicker as well. After the short setup, you now land straight on your home screen with a Getting Started agent ready to open — no guided walkthrough to sit through. Sage, your setup helper, is always one click away with the Ask Sage button whenever you want a hand.

Behind the scenes

Mac downloads are signed and checked by Apple before they reach you, updates on Mac install automatically like they do on Windows, and a round of security housekeeping cleared every open advisory in the app's building blocks.

[0.9.0-beta.1] — Safety that's always on

EasyCC now keeps a much closer eye on your sensitive information. It watches for things like card numbers, ID numbers, passwords, and personal details in what Claude reads — and in what you send — and hides or blocks them before they ever leave your computer. It also spots hidden instructions that people sometimes plant in web pages or documents to trick an AI assistant, and stops Claude from acting on them.

These protections are now always on for everyone and can't be switched off, so you're covered from the start. You can see exactly what's being caught, and how your connection is protected, in Settings → Safety.

Behind the scenes

The checks that matter most now happen right at the connection to the AI, so anything sensitive is caught before it leaves your machine rather than after. Coverage depends on how you connect — the Safety screen tells you plainly whether yours is fully protected.

[0.8.5-beta.3] — Auto mode by default

New chats now start in Auto — Claude handles routine steps on its own and only pauses for the things that deserve a look, so you spend less time approving and more time working. You can switch to Act or Plan anytime from the mode button next to the message box. Auto needs a capable model, so it stays on Act if you've picked the lightweight one.

Behind the scenes

EasyCC now reads PowerShell commands, not just Bash, so the same folder guardrails apply on Windows: a command that would write outside your agent's folders, change a "view only" folder, or adjust a Windows system setting now asks for your okay first instead of running on its own.

[0.8.5-beta.2] — Auto mode that doesn't interrupt your skill-building

In Auto mode, creating a new skill no longer pauses to ask for permission — building your agent's own skills is exactly what Auto is meant to do, so it just gets on with it, while still checking with you on anything genuinely risky.

Behind the scenes

Security hardening to the guardrails that keep Claude working only inside the folders you've chosen, plus stronger protection for EasyCC's own internal files.

[0.8.5-beta.1] — A hands-off mode for routine work

Chat gets a third way to work, alongside Plan and Act: Auto. In Auto, Claude carries on with routine steps on its own and only pauses to check with you on the things that genuinely deserve a second look — deleting files that were already there, or sending your information somewhere outside your folders. You'll find it in the mode button next to the message box.

Everyday work inside your agent's folders — reading, writing, editing — flows without interruption, while the boundaries that keep Claude inside your folders stay firmly in place. Auto needs one of the more capable models, so it's hidden when you've switched to the lightweight one.

[0.8.4-beta.8] — Always working from your latest files

When you share a Word document, spreadsheet, or PDF with an agent and later replace it with a newer version, EasyCC now reads the new one instead of quietly sticking with the old copy. Right-click any shared file — or its folder — and choose Re-read latest version to refresh it on the spot, or just ask Claude to use the latest version of a file and it'll pick up your changes. This fixes the frustrating case where you swapped in a corrected file but the agent kept answering from the one you replaced.

Also in this release

• A disconnected folder no longer freezes the app. If you've linked a folder that lives on a network or external drive and it isn't connected, EasyCC used to hang while it waited — sometimes for a minute. Now the rest of your agent keeps working, that one folder is marked Unavailable, and you can reconnect and hit Try Again.
• A clearer path when a reply gets blocked. If your organization's AI connection blocks an answer with a content-policy filter (that's a setting on your connection, not EasyCC), the notice now says so plainly and offers a one-click Try again — which often goes through, since the next reply is usually worded differently.

[0.8.4-beta.7] — Set up connected tools just by asking

Some connected tools — AutoCAD, for example — need to know which folders they're allowed to work in before they'll touch your files, and there was no way to set that up without hand-editing a settings file. Now you just ask: tell Claude something like "let the AutoCAD connector use my Drawings folder" and it sets it up for you, with a quick confirmation each time. You can also do it yourself anytime in Settings → Connectors, using the ⋯ → Edit settings menu on any connector. Secret values like API keys live in that same screen, kept in your computer's password vault rather than a plain settings file.

[0.8.4-beta.6] — Answers that show their sources

When Claude answers using one of your files or a web page it looked at, it now links straight back to the source so you can open it and check for yourself. Ask something that draws on a document in your agent, and the answer points to the exact file — click it to open in EasyCC. Web research gets the same treatment: the page Claude used becomes a clickable link instead of a name you have to go hunting for.

[0.8.4-beta.5] — Rename your chats

You can now give your chats names. If you keep one conversation per project, this makes it easy to spot the right one later: hover any chat in the "Recent conversations" list and click the ⋯ menu (or right-click it) → Rename. The name sticks and shows up every time you come back. Renaming an open chat from its tab works the same way, and both now tell you if a rename couldn't be saved instead of failing quietly.

Also in this release

• Connectors tell you when they don't start. If one of your connected tools fails to launch, EasyCC now shows a plain-English notice naming it, instead of quietly carrying on without it. Connector commands that rely on the bundled runtime also resolve more reliably.
• Chats that can't start now say why. A conversation that failed to launch used to just sit there spinning. Now it surfaces the reason so you're not left guessing.
• Folder fixes. Removing a linked folder no longer blocks you from adding a new one, and a folder that's gone missing no longer stops a chat from starting.

Behind the scenes

Security and dependency updates to the admin web app, plus a batch of test- and build-reliability fixes.

[0.8.3-beta.3] — PDF indexing of newly-added directories

Follow-up to 0.8.3-beta.2. After linking a folder to an agent (file tree → "Add directory"), PDFs inside the new folder weren't being indexed until you closed and reopened the agent. Adding a stack of scanned PDFs and immediately asking Claude to search them just returned empty results.

The PDF indexer's "rescan on add" trigger was wired into a store action that nothing actually called — the file-tree UI invoked the IPC directly and bypassed it. Fixed by triggering the indexer at the actual call site, so newly-linked folders start getting fingerprinted + OCR'd within a few seconds of linking.

Also added internal diagnostic logging so a quietly-failing agent config no longer makes the indexer report "found no PDFs" without a clue why.

[0.8.3-beta.2] — PDF processing fix for the Full installer

Hotfix for v0.8.3 / v0.8.3-beta.1 on Windows. If you installed the Full variant (the larger setup that bundles Claude Code, Git, and Node so you don't have to install them separately), PDF text extraction, OCR, and page rendering all silently produced empty results — attaching a PDF wrote a text.md cache file with zero bytes in it.

The cause was a build-script regression: scripts/configure-full-build.js was overwriting Tauri's bundle.resources instead of merging into it, which dropped the bundled PDFium library out of the Full installer. The Lite installer was unaffected.

What's fixed

• Full installer now ships PDFium. PDF text, OCR for scanned PDFs, and inline page rendering all work again.
• Visible error if PDFium is ever missing. EasyCC now probes for the bundled library at startup and shows a persistent toast pointing at a reinstall, so a future packaging regression can't silently fail again.
• Build-time guard. A new scripts/verify-bundle.mjs step runs in CI after every Windows / macOS build and fails the release if PDFium isn't where it should be.

Migrating from v0.8.3 / v0.8.3-beta.1 (Full installer only)

Reinstall over the existing app — auto-update will pull v0.8.3-beta.2 and the new installer carries PDFium. Existing PDF cache files (the empty text.md ones) are detected as stale on the next attach and rewritten with the actual extracted / OCR'd text. Lite installer users can ignore this release.

[0.8.3] — PDF handling rework

Drag-and-drop a stack of PDFs into chat — even hundreds of them — and ask Claude questions across all of them. The cost used to scale with the number of pages you uploaded; now it scales with the question Claude needs to answer.

What changed

• Auto-indexing of every PDF in your agent. When you open an agent, EasyCC walks the agent folder and any folders you've linked, fingerprints each PDF, extracts its text, and runs OCR on scanned ones. Subsequent chats can search across all of them with a single Grep — no need to attach individual files. A small chip near the bottom of the file tree shows progress while it runs.
• Faster sends with multiple PDFs attached. Up to three PDFs process in parallel instead of one at a time. A four-PDF send that used to take 4 minutes now takes about 1.
• No more "Reading 99 of 172…" interruptions during background work. OCR for indexed PDFs runs silently. The "Reading X.pdf" indicator only shows when you're actually attaching a file in chat.
• Resumable indexing. Close the app mid-processing or switch agents — when you come back, indexing picks up where it left off. PDFs already finished are skipped; partial work is correctly retried.
• Friendlier failure messages. Attaching too many PDFs at once now shows a clear toast instead of silently failing. Files in linked directories now show their real size in the attachment chip (was showing "0 B"). PDFs that can't be read direct Claude to the cached version instead of producing a cryptic pdftoppm not found error.

Under the hood

• Cache moved from .easycc/.cache/pdfs/<hash>/ to .easycc/pdfs/<slug>/. Slugs are derived from filenames (e.g. api-rp-521-2022/) so paths are readable and don't trip gateway secret-scanners that pattern-match on long hex strings.
• Content fingerprint switched from sha256 to xxhash3 (16 chars instead of 64) — same dedup quality at single-user scale, ~10× faster, and short enough not to look like a credential.
• Path validator inverted: .easycc/ is open by default with a small explicit deny list (versions.db, blobs/, config.json). Adding new derived-data trees no longer requires updating carve-outs.
• Background indexer is sequential per-PDF for predictable RAM (PDFium's per-document peak doesn't stack); cancellable per-agent with progress events streamed to the frontend.

Migrating from earlier versions

• Existing .easycc/.cache/pdfs/ directories are left in place but ignored. They can be deleted to reclaim disk space.
• The first time you open an agent on v0.8.3, the indexer runs against everything reachable. For a typical agent of a few hundred PDFs, expect minutes; for a large reference library (1000+ scanned PDFs) it can run for hours in the background. The app stays fully usable while it does.

[0.8.1-beta.3] — Per-user Windows install restored

The v0.8.0 / v0.8.1 series switched the Windows installer to machine-wide install mode to support enterprise / MDM rollouts. That choice broke a core assumption for individual users: the installer asked for admin elevation on every install and every auto-update, and standard-user Windows accounts couldn't update at all.

This release reverts the consumer installer to per-user install (installMode: currentUser):

• No more UAC prompt when installing or auto-updating EasyCC.
• Auto-update works on standard user accounts again — no IT escalation needed.
• EasyCC installs to %LOCALAPPDATA%\EasyCC (the same path v0.7.x used).
• If you already updated to v0.8.0 / v0.8.1-beta.1 / v0.8.1-beta.2 the old install lives in %ProgramFiles%\EasyCC and won't auto-migrate onto v0.8.1-beta.3. Open Settings → Apps, uninstall the existing EasyCC, then download v0.8.1-beta.3 fresh from Releases. Your agents and history live outside the install folder, so nothing is lost.
• Enterprise machine-wide deploys are temporarily paused while we ship a separate per-machine installer variant that doesn't force consumer users to elevate. Tracked on the roadmap.

[Unreleased] — Enterprise deployment

This release introduces everything an IT admin or service-provider partner needs to deploy EasyCC across a fleet and hand users a fully configured first launch. See docs/enterprise/ for the full guide.

Phase 2 — coverage of new user-configurable features

Extends the admin tooling to cover the safety scanner and token-efficiency features that shipped on dev after the original Phase 1 branch.

New managed policy fields (10 total)

• Safety scanner (5): safety_deep_check_enabled, safety_sensitivity, safety_judge_mode, safety_block_mode, safety_custom_model_url_base
• Token efficiency (5): one lock per behind-the-scenes saver — expanded_tool_output_limits, skill_model_routing, read_once_hints, mcp_classifier, local_proxy

Fixed

• Claude permissions panel now merges user + project + local scopes (matches Claude Code's own runtime cascade).
• Claude settings UI now reads/writes the isolated claude-home/settings.json so admin overlays and user edits target the same file Claude subprocess reads.

See the phase 2 sections in docs/enterprise/policy-reference.md and docs/enterprise/service-provider-bundle.md for full reference + examples.

New — Admin controls

• Managed configuration on Windows and macOS. IT admins push settings via Intune, Jamf, Kandji, Workspace ONE, Group Policy, or any tool that writes to HKLM\Software\Policies\EasyCC / /Library/Managed Preferences/com.easycc.app.plist. Matches Chrome Enterprise conventions — enforced values at the top level, recommended defaults under a sibling container.
• "Managed by your organization" lock icon. Locked settings render disabled in the Settings UI with a clear plain-English tooltip. Users see what's controlled and why, and the backend rejects writes to enforced fields even if the WebView is out of date.
• Update channel + endpoint overrides. Admins can pin a fleet to stable, point at a self-hosted mirror URL, and verify the signing key fingerprint in Settings → About for compliance auditing.
• Update deferral + forced install. max_update_deferral_hours caps how long users can dismiss the banner; force_update_after_hours makes the update mandatory with a countdown.
• Paste-ready policy templates. Intune Settings Catalog JSON, Jamf .mobileconfig, Windows Group Policy ADMX/ADML — all under docs/enterprise/.

New — Service-provider pre-seed bundles

• Ship a bootstrap.json alongside the installer (or via MDM) and EasyCC pre-configures itself on first launch. No setup wizard, no pasting keys, no MCP server dialogs.
• Agents, Skills, and MCP servers (stdio, http, sse — all three transports) can be defined per-Agent inline, or at user scope shared across every Agent.
• Provider config (Anthropic Account, API Key, Custom Gateway, Bedrock, Vertex, Foundry) is applied automatically. Credentials are resolved via secret_ref URIs from the OS keychain — never included in the bundle file.
• Branding — org name in the title bar, welcome message on the setup screen.
• Idempotent. Per-bundle and per-section markers mean re-launches don't duplicate state, and partial failures retry only the missing pieces.
• Full schema + authoring guide at docs/enterprise/service-provider-bundle.md.

New — Installer

• Windows installs are now machine-wide (installMode: perMachine). A single install covers every user account on the workstation. Required for Intune / SCCM fleet deploys. Reverted in v0.8.1-beta.3 — see top of changelog. A separate enterprise installer variant is on the roadmap.
• NSIS bundle passthrough. If bootstrap.json ships alongside the installer, the post-install hook copies it to %PROGRAMDATA%\EasyCC\ and registers a BundlePath pointer under HKLM\Software\EasyCC.
• --silent-first-run CLI flag. Tells EasyCC it's being started by a deploy tool so interactive onboarding is safely skipped when a bundle already satisfies setup.

New — Documentation

• docs/enterprise/README.md — audience overview + 10-minute deployment checklist.
• docs/enterprise/policy-reference.md — every managed setting with type, enforceability, and examples.
• docs/enterprise/silent-install.md — Windows / macOS silent install flags.
• docs/enterprise/self-hosted-updates.md — how to mirror EasyCC's signed update feed.
• docs/enterprise/service-provider-bundle.md — full bundle schema and secret_ref URI grammar.
• docs/architecture/enterprise-deploy.md — developer-facing architecture of the managed policy + bundle layers.
• docs/architecture/testing-bundles-locally.md — dev testing guide with a reference bundle you can copy-paste.

Known limits for v1

• Logos are text-only in branding. SVG rendering waits on a safe sanitizer; a logo field is not in the v1 bundle schema.
• Linux is not supported for managed configuration or the bundle system.
• Self-hosted update mirrors must serve EasyCC's signed manifest byte-for-byte — re-signing with your own key isn't supported yet.
• secret_ref URIs support keychain: only. env:, oauth:, provision:, prompt: schemes return a clear upgrade-required error and are planned for v2.

April 2026 Update (v0.8.0-beta.7) — 2026-04-18

New

• Safety scanner — EasyCC now checks every tool result Claude receives — web pages, files, connector output — for hidden instructions that could try to trick Claude. A lightweight cleanup step always runs, and you can turn on a stronger on-device checker or ask Claude Haiku for a second opinion. See Settings → Safety to configure it or watch what it's caught in the activity log.

Improved

• Smaller, faster safety checks — the optional prompt-injection detection model dropped from ~700 MB to ~360 MB, and per-scan time went from 10–16 s to 1–3 s. Turn it on under Settings → Safety if you didn't before.

April 2026 Update (v0.6.1-beta.1) — 2026-04-06

New

• 62 skills ready to use — Browse skills by category, search by name, and quickly re-run recently used skills. New skill packs for knowledge workers, engineers, and creators.
• Open 120+ file types — View PDFs, Word docs, spreadsheets, images, videos, 3D models, and more right inside EasyCC. No need to switch apps.
• MCP integrations — Connect external tools and services to expand what Claude can do in your workspace.
• Additional workspace folders — Add folders from anywhere on your computer to your workspace, not just files inside the project.
• Multi-agent system — Claude can now use specialized agents behind the scenes for faster, higher-quality results.

Improved

• Smarter AI learning — Overhauled the learning system so EasyCC better remembers your preferences and habits over time.
• Chat stability — More reliable conversations with improved message handling and resumed conversation formatting.
• Apple-signed installer — macOS builds are now signed and notarized for a smoother install experience.
• Windows-signed installer — Windows builds now use EV code signing for trusted installs.

Fixed

• Fixed rendering issues and markdown file links on Windows.
• Fixed edge cases in file permission handling.

March 2026 Update (v0.6.0-beta.1) — 2026-03-26

New

• MCP integration manager — Browse, install, and configure MCP servers from within EasyCC.
• Additional workspace directories — Add external folders to your workspace sidebar.
• Chat improvements — External file attachments in chat, better message formatting, and stability fixes.

Improved

• Dev tooling — New MCP dev server for runtime observability during development.
• UI/UX polish — Comprehensive audit and fixes across the app interface.

Earlier Releases

v0.5.4-beta (February–March 2026)

• AI learning system with habit tracking and heuristic analysis
• Permission system overhaul for safer file operations
• Claude settings manager
• Resumed conversation formatting improvements

v0.5.3-beta (February 2026)

• Search across workspace files
• Auto-update system with beta/stable channels
• File tree performance improvements

v0.5.0–v0.5.2 (January–February 2026)

• Integrated terminal (run commands without leaving EasyCC)
• Version history with checkpoints
• Skill runner for AI-powered tasks
• Setup wizard and onboarding flow
• User registration and authentication