Post-upgrade check

Codex CLI · gpt-5.6-sol agent on u-corp

Description

My notes

Private to this console — never sent to u-corp. Saves automatically.

Conversations

No conversationsopen right now
The fleet manager reports this agent's conversation count but does not yet attribute individual conversations to an agent, so they are not listed here. Every conversation in the fleet is on Conversations.

Storage on u-corp

Configuration directory
/home/u/.aiclisupervisor/agents/agt-adfa0de4dc5b/config
Shared by every conversation of this agent — this is where its harness sign-in lives.
Initial working directory
/home/u/.aiclisupervisor/agents/agt-adfa0de4dc5b/template
Copied into a fresh directory for each new conversation, so conversations never interfere with each other.
2 conversation workspaces are stored on this agent's host. Every conversation gets its own copy of the agent's initial working directory, and the copy is kept when the conversation ends because it holds that conversation's work. This console has no way to reclaim them yet — the count only grows, and the space is freed only by deleting the agent with its files, or by clearing the directories on the host. A time-based reclaim is planned for a later increment.

Details

Agent idagt-adfa0de4dc5b
Harnesscodex-cli
Modelgpt-5.6-sol
Supervisorurl://vpn.u-corp.aiclisupervisor/
Agent home/home/u/.aiclisupervisor/agents/agt-adfa0de4dc5b
Tools
Register lambda functions so the fleet's AI-CLI sessions can call them as MCP tools or CLI commands. Functions that require a W3Wallet credential are gated: each conversation's first use files a request here, and a grant (or revocation) takes effect immediately without restarting the session. The tool registry is shared by the whole fleet.

Register a lambda function

Registered tools

Loading tools…

Pending credential requests

Loading credential requests…

Active grants

Loading grants…

Danger zone

Delete this agent
Removes Post-upgrade check from u-corp, so it can no longer be given conversations. You can also erase its files, which is what destroys its harness sign-in and the work held in its retained conversation workspaces. Neither can be undone.