Changelog

Summary

Effigate now has a public website, separate from the signed-in app, for anyone who wants to understand the product before creating an account. It covers what Effigate does for different teams, shows real use cases, and gives new visitors a straightforward way to ask for access.

What You Gain

Previously, there was nowhere to send a colleague, a prospect, or your own manager who wanted to understand Effigate without already having a login — the product only existed behind sign-in. Now there's a proper front door: a homepage that explains what Effigate does, dedicated pages for how Engineering, Finance, Operations, Sales & Marketing, and Support teams each use it, and a use-cases page you can filter by scenario. If you're already signed in, visiting the site still takes you straight into your workspace, so nothing changes for existing customers.

How It Works

• Solutions by team — five pages tailored to how each function actually uses Effigate day to day.
• Filterable use cases — browse real scenarios instead of a generic feature list.
• A waitlist with a live signup count — request access and see how many others already have.
• About, Brand, and Privacy pages — the background information teams ask for before adopting a new tool.

Where to Find It

The site is live now at the Effigate domain for anyone not yet signed in. No account or configuration is needed to browse it.

See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center for yourself.

Summary

A project running for a while accumulates documents fast, and until now the Documents tab was one long, unfiltered list. It now has category and visibility filters, multi-select with bulk delete, and a merge tool that combines several documents into one.

What You Gain

Scrolling a long, flat list to find one document, or to clean up several that had grown redundant, wasted time that should have gone into the actual work. Now you can narrow the list in a couple of clicks, act on several documents at once, and consolidate overlapping ones instead of deleting and rewriting them from scratch.

Picture a project with a dozen scattered reference documents built up over months. With filters, you can narrow instantly to just the ones marked for agent use. With multi-select, you can tidy up outdated ones in one pass. And with merge, three overlapping documents become one clear document, with its content and visibility preserved — so tidying up never risks quietly losing information an agent was relying on.

How It Works

• Filter by category and visibility. Narrow the list by document category and by whether a document is always available to agents or only fetched on demand. A search box matches titles and summaries, and a Clear button resets everything.
• Select several documents at once. Tick documents individually or select all within your current filter.
• Delete in bulk, with a confirmation step before anything is removed.
• Merge into one. Combine selected documents into a single document — you choose its title and category, and you see exactly what it will contain before confirming. A merged document stays visible to agents if any of its parts were, so merging can never accidentally hide information an agent depended on.
• A more accurate token estimate. The figure showing how much of an agent's context your always-available documents use now reflects exactly what agents actually receive, rather than counting documents that don't reach them at all.

Where to Find It

Open any project's Documents tab to use filters, multi-select and merge — available now on every project.

See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.

Summary

Everything that needed a decision from you used to be scattered across the app — a question buried in one task's comments, a ready pull request on another, a failed run somewhere in the Inbox. A new Decisions page gathers all of it into one ranked list, and keeps it current automatically.

What You Gain

Answering "what actually needs me right now" used to mean checking several different places and hoping you hadn't missed one. That kind of scattered attention is exactly how small blockers sit unresolved for longer than they should, quietly slowing down whatever depends on them.

Now there's a single place: agent questions that stopped a run, failed runs that couldn't recover on their own, agents waiting on a local directory, pull requests ready to merge, and blocked tasks — all in one list, ranked by how stuck each one is. Clicking an item opens the task directly so you can act without navigating away.

How It Works

• Items are ordered by urgency: stalled work waiting on you comes first, followed by finished work ready to be released, then the rest.
• There's no dismiss button — an item leaves the list only when the real situation is resolved, wherever that happens: here, on the board, or on GitHub.
• The list updates itself both ways: new items appear as they arise, and resolved ones disappear immediately, moving you straight to the next item if you were working through the list.
• It sits alongside the Inbox but serves a different purpose — the Inbox shows what already happened, while Decisions shows only what is still waiting.

Where to Find It

Open the Decisions page from the main navigation — available now for every account.

See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.

Summary

A correctly configured local project directory could still go unused if you had more than one machine connected under the same account — agents would fall back to a fresh checkout instead, sometimes failing outright if the project's other resource needed access the fallback machine didn't have. It now always reaches the specific machine it was set up for.

What You Gain

If you run more than one connected machine — say, a Mac and a Windows machine both set up for the same account — this previously meant Effigate Command Center couldn't reliably tell which one actually held your local directory, and could pick the wrong one. Now the exact machine that claimed the task is the one that's used, every time, regardless of operating system.

Where to Find It

This fix applies automatically — no changes needed to your existing local directory setup.

See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.