v3.1.5: Every Computer Gets a Name You Choose, New Employees Join the Team on Day One, and Chat Bubbles Turn to Frosted Glass

A small release with one change worth acting on today. Version 3.1.5 makes it impossible for an employee to send a desktop action to the wrong computer, lets you give every paired computer a nickname, connects new employees to their team from their first minute, and gives chat wallpapers a lighter, frosted look.

If your employees control more than one computer, skip to the security section first. There is a one-click step for existing employees.

Security: one name, one computer, no guessing

Since v3.1.2, an employee can be paired with several computers and picks one by name. That works well until two machines share a name. It happens more often than you would think: two servers both called "SRV01", two laptops imaged from the same template, an old workstation and its replacement.

In that situation the employee had no way to tell the machines apart, and an action addressed to "SRV01" went to whichever of the two happened to be online. A task meant for one server could run on the other. On a feature that clicks, types and runs things on real machines, "probably the right one" is not good enough.

From 3.1.5, the rule is simple:

• A name that matches more than one paired computer is refused, and nothing is sent. This applies whether those computers are online or not, and the match ignores upper and lower case, so "srv01" and "SRV01" count as the same name. The employee gets a clear explanation and the list of matching computers.
• The same refusal applies when the employee names no computer at all while its paired computers share a name. It will not pick one for you.
• Every computer now has a visible id, shown in the employee's status check, and the employee can target a computer by that id. So a precise action is always possible, even before you tidy up the names.
• Your employee will not rename your computers. If it notices a clash, it suggests a nickname and leaves the decision to you.

What you need to do: existing employees pick up this protection through Skills > Reinstall. New employees have it already. If any of your employees use the desktop app on more than one machine, it is worth the ten seconds.

New: give each computer a nickname

The refusal above is the safety net. The nickname is what keeps you out of it.

In Configuration > Connectors > Desktop, every paired computer now has a Rename button. The nickname you choose is the name your employees use to target that machine, so "Accounting laptop" and "Build server" replace two identical "SRV01" entries.

A few details we got right so you do not have to think about them:

• The nickname sticks. It survives the desktop app reconnecting, the computer being paired again, and its key being renewed.
• Nicknames are unique. A name already used by another of your computers is refused, so you cannot recreate the clash by accident.
• The original machine name stays visible next to the nickname, so you always know which physical box you are looking at.
• Clashes are flagged. Computers that share a name show a warning asking you to give one of them a nickname.
• Clearing a nickname returns the computer to its machine name.

The Rename button is available in all 10 interface languages.

Changed: new employees join the team by default

Until now, a newly created employee started out Team Isolated: no access to the shared Team Workspace and no delegation to or from its colleagues. Most people wanted the opposite, and had to reconnect each new hire by hand. Some never noticed, and wondered why their new marketing employee could not pass work to the analyst.

From 3.1.5, a new employee joins the team from its first minute. It can read and write the Team Workspace and delegate with its teammates straight away. If you want an employee to work on its own, for a confidential client or an experiment you want kept separate, turn on the Team Isolated switch for that employee.

Nothing changes for the employees you already have. They keep their current setting. A cloned or transferred employee keeps the setting of the original, so copying an isolated employee gives you another isolated employee. Nova, the in-app help, has been updated to explain the new default.

Changed: chat backgrounds get frosted glass

The owner-chosen chat backgrounds from v3.1.3 looked good on their own and less good with a conversation on top. With a pattern or picture behind them, messages sat on solid cards only a few pixels apart and had no outline. On a busy wallpaper they read as heavy blocks stuck together.

Messages now sit on frosted glass:

• more space between messages,
• a fine outline and a soft shadow,
• the wallpaper showing through behind each message, softly blurred,
• a small corner on the author's side, so each bubble points to whoever wrote it.

Your own messages are tinted with the interface colour, never the wallpaper's, so who is speaking reads at a glance whatever background the owner picked. The built-in chat themes such as Classic and Cloud keep their own colours.

In short

• Security: a computer name shared by several machines is now refused instead of guessed. Existing employees get this through Skills > Reinstall.
• New: nickname any paired computer in Configuration > Connectors > Desktop.
• Changed: new employees join the team by default. Existing ones keep their setting.
• Changed: chat messages over a wallpaper are lighter, more spaced and easier to follow.

Want to test the most advanced AI employees? Try it here: https://Geta.Team