InfraStudio Agents

Changelog

What has shipped.

User-visible changes to InfraStudio Agents, newest first.

Last updated

Readable analytics recordings with credential masking

Session recordings retain the page styling and account context needed to understand a visit. Recognizable keys, passwords and tokens stay masked, and connection-code and file-input areas stay excluded. Analytics preferences still control whether recording starts.

GitLab keys stay with their destination

A project token is tied to the GitLab address it was entered for. Changing that address requires a new token; a settings form opened before the change cannot silently restore the old destination.

Slow integrations leave room for other workspaces

Calls to a project's own GitLab or integration host have bounded deadlines and response sizes. A slow host gets a cooldown, keeping shared runner work available to other customers.

Messaging follows workspace membership

Removing a member revokes their linked Telegram command access. Member-owned private-chat linking keeps the connection attached to the correct person, and Telegram commands are recorded in the audit log.

Stricter GitLab CI and safer posted text

Manual or skipped pipelines no longer count as passing merge CI. Agent-written GitLab notes and merge-request descriptions are treated as text, and agent patches cannot change GitLab CI definitions.

Set up a project or learn who operates the service.