#agent2
The DHORKS should have anticipated that the imps would be back to teach them a lesson, but at least they make a dynamite pair of ladies ;3

A wonderfully mean gift from @natsuchu.bsky.social !

#helluvaboss #hellaverse #bondage #bdsm #forcefem #dhorks #agent1 #agent2 #nsfw #rule34 #coupleindistress
November 16, 2026 at 2:15 AM
Day 12: Teasing & Day in the Life of (Paimon)

Featuring a bit of irl Paimon trivia.

"Agent Two didn't expect a camel ranch."

#PaimonWeek #PaimonWeek2026 #NoHurtHellvember #Paimon #agent1 #agent2 #dhorks #helluvaboss

ellipsus.com/read/2m599PQ...
Day 12: Teasing & Day in the Life of (Paimon) | Giza20 | Ellipsus
Ellipsus makes it easy for anyone to write together.
ellipsus.com
November 13, 2026 at 9:44 PM
Maybe if Trump would announce he was parachuting in on his next visit to wherever, people would show up

Agent1 to Agent2: Did you check the parachute?
Agent2: POTUS wanted to do it himself
A1: And you let him?
A2: YEP!
A1: Guess our jobs are done, he shoulda done this sooner
A2: YEP!

#VOTEBLUE
October 21, 2026 at 10:24 PM
Can you unpack that?

For what it is worth, senior professors have not manually checked a lot of code that has been written by their lab members.

You can set up AI agent2 to do adversarial review of code produced by agent 1. Have agent 3 make a patch based on agent 2's review and repeat...
October 22, 2026 at 12:45 AM
Zabbix Agent2's built-in Docker plugin pulls container CPU, memory, network and block IO straight from the Docker socket, no scripts needed. https://www.valtersit.com/vault/monitor-docker-container-metrics-with-zabbix-agent2-plugins-e86c1e/
Monitor Docker Container Metrics with Zabbix Agent2 Plugins
www.valtersit.com
October 20, 2026 at 11:50 AM
What have my favorite guys been up to for the past 2 years??? Idk probably some bullshit.
Manifesting them so hard in s3 AUUGUFHFHFHHH 🥰🥰🥰🥰😫

#helluvaboss #helluvabossfanart #agent1 #agent2 #dhorks
October 1, 2026 at 5:41 PM
🔧 Systèmes : Agent2 versions antérieures à 7.0.31
September 24, 2026 at 1:35 PM
Agent-2 | 90 stars | 5 forks

Agent2 — An autonomous AI agent for coding, cybersecurity, terminal automation, and intelligent task execution.
Agent-2 - Trending on te9.dev
Agent2 — An autonomous AI agent for coding, cybersecurity, terminal automation, and intelligent task execution.
repotrend.com
September 20, 2026 at 5:48 AM
we're creating stubs of everything in crow_cli/{agent2, mcp2, client2} to build a mental model of what we want to do before filling in blanks.
ACP v2 is landing in python-sdk!
September 13, 2026 at 5:08 PM
Обеспечение работы ИИ-коммерции с новым протоколом Agent Payments Protocol (AP2)

Компания Google представила протокол Agent Payments Protocol (AP2) - открытый стандарт, предназначенный для безопасных транзакций с участием агентов. Этот протокол основан на существующих фреймворках Agent2…

#ai #news
Powering AI commerce with the new Agent Payments Protocol (AP2)
cloud.google.com
September 29, 2025 at 12:54 AM
My fav bits of newsletter:

🤖 Agent2Agent protocol
🤖 Google’s Customer Engagement suite
🤖 o3 is really good
🤖 Google is using AI to communicate with dolphins (perhaps pets are next?)
🤖 New Brain computer interface is a 4mm implant inserted in scalp skin

community.mariehaynes.com/posts/agent2...
Agent2Agent protocol, Customer Engagement Suite, o3 (wow), Astra in glasses demo, AI communicating with dolphins - Apr 14, 2025
Hello! 👋Holy Moly a lot has happened. Google shared more on AgentSpace, Agent2Agent Protocol and The Customer Engagement Suite. It’s hard to wrap our minds around how communication on the web is ab...
community.mariehaynes.com
April 21, 2025 at 5:21 PM
CERTFR-2026-AVI-0498: Multiples vulnérabilités dans Zabbix Agent2
https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0498/
April 27, 2026 at 12:00 PM
From Casual Jumping to Casual Cleanup
https://www.youtube.com/embed/hh3V9RMVe08

The weekly indie showcases highlight the games we play on stream, all games shown are either press keys or demo submissions.

0:00 Intro00:14 Anomaly Agent2:16 Ak-Xolotl4:35 Ve Than: Divine Guardian6:12 Dream of […]
Original post on wrestling.social
wrestling.social
March 3, 2025 at 6:33 PM
May 15, 2025 at 11:27 PM
人間がレビューすることも考えると
結局はローカル上に複数のagentを立てて、それぞれ重ならない範囲で作業させるのが今の自分のベスト

agent1: 機能開発
agent2: テスト作成
agent3: レビュー
agent4: 調査

みたいに1つのWorkspace内で作業分担させてる

コンテキストスイッチも少ないですし
May 18, 2025 at 11:50 PM
Im happy to share with you my designs for the @hell MerMay collaboration!!!!

This is one of my favorite collabs so far 🥰

It came out INCREDIBLE because everyone is such an amazing artist!

Check the complete collab here: acggoods.com/artist/Hell-...

#Millie #Salina #Agent2 #HellACollab #MerMay
May 3, 2026 at 4:18 AM
Happy Mar13 Day! Did hypno Marie last year so this time around I decided to draw my rendition of agent 2 instead.

#Splatoon #Splatoonart #art #fanart #Marie #Agent2
March 13, 2026 at 2:33 PM
More agent design stuff with Marie this time. Wanted to make her a sneaky sniper with the ghillie suit.

#Splatoon #SplatoonArt #Art #Fanart #Marie #Agent2
July 31, 2025 at 4:25 PM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 14, 2025 at 1:27 AM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 14, 2025 at 1:27 AM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 7, 2025 at 1:21 AM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 6, 2025 at 11:14 AM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 6, 2025 at 11:14 AM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 4, 2025 at 5:27 PM
Parabola GNU/Linux-libre: 'zabbix' users: manual intervention may be required
From Arch: Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system].
parabolagnulinux.org
August 4, 2025 at 5:27 PM