Palzin LLC

Changelog

Everything we shipped in September 2026.

Sep 21, 2026
fixed

Disconnected Machines No Longer Show As Online Forever

Summary

The desktop app and CLI check in periodically to confirm a machine is still connected. A machine that never completed that first check-in at all — rather than one that simply went quiet after connecting — was being skipped by the process that marks disconnected machines offline, so it could stay listed as "online" indefinitely. It's now treated the same as any other disconnected machine.

What You Gain

Before this fix, most disconnected machines were correctly marked offline a few minutes after they stopped checking in — but a machine that had never successfully checked in even once fell through a gap in that process and could sit listed as online with no end in sight. That's misleading when you're deciding where to send work, or trying to understand whether a machine is actually available to pick up a task.

Now every machine is held to the same standard: if it hasn't checked in recently, including a machine that never checked in at all, it's marked offline so your list of available machines reflects reality.

How It Works

  • Machines that never checked in are now treated the same as ones that went quiet — both are marked offline once they're overdue.
  • This runs automatically as part of the regular check that keeps machine status up to date; there's nothing to configure.
  • A one-off cleanup pass also corrected any machines left incorrectly marked online from before this fix.

Where to Find It

Machine status is shown wherever you view your connected runtimes; it now updates reliably with no action needed from you.

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

D
Dev Team
Be the first to react
Sep 3, 2026
fixed

Managers Can Now Update Any Teammate's Agent Settings

Summary

Agents can be shared across a team, but a manager adjusting a shared agent's execution settings — such as which model it uses — could run into an error if that agent happened to run on a teammate's machine rather than their own. That's fixed: the save now goes through correctly.

What You Gain

Shared agents are meant to be manageable by anyone with the right permissions, not just the person whose machine they happen to run on. Before this fix, a manager trying to tweak a shared agent's settings got blocked by an error entirely unrelated to whether they were actually allowed to make the change — simply because the agent's machine belonged to someone else. That meant asking the machine's owner to make the change instead, even when the manager already had full permission to manage the agent.

How It Works

  • Saving an agent's existing settings now works regardless of who owns its machine — only an actual change to which machine it runs on is checked against ownership.
  • Managers and admins can move a shared agent onto any machine in the company, consistent with their existing ability to edit any agent.
  • If you try to move an agent to a machine you're not allowed to use, you now get a clear message on that field, instead of a generic error.

Where to Find It

This applies automatically wherever you manage an agent's Execution settings — there's nothing to turn on.

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

D
Dev Team
Be the first to react