The full journey of one task in PugPort
PreviewA four-step preview of the format. The full explainer is coming soon. Accounts and usage numbers are illustrative.
A task arrives
You describe what you need in one chat: rename 400 trip photos by date and place. PugPort reads how much usage each of your signed-in accounts has left.
It picks the account with the most room
PugPort picks the account, model and effort from the task and from how much usage each one has left. Codex (work) has the most room, and an everyday task gets GPT-6.1 Sol at medium effort.
The account hits its usage limit
Partway through, Codex (work) runs dry. The photo dates and places are read and the new names are prepared, but not yet applied.
The work moves on with a handoff note
PugPort passes the work and a checked handoff note to the account with the next most room, Claude Code (work), which applies the names and checks the count. Pin an agent and it stays put.
You
Rename the 400 photos from our Lisbon trip by date and place.
All 400 photos are renamed by date and place. Final count: 400 photos, no duplicate names.
PugPort
Reading usage on every account
Running on Codex (work)GPT-6.1 Sol · medium
most room + everyday task → GPT-6.1 Sol, medium
- Read the photo dates and places
- Prepared the new names
Usage limit reached.
Codex (work) reached its usage limit.
Usage limit reached.
Codex (work) reached its usage limit. Continued on Claude Code (work).
Codex · Sol → Claude Code · Opus
Completed: metadata check and name preview. Next: apply the names and verify the photo count.
Your accounts
- Codex (work)91% leftCodex (work)0% leftResets in 2h
- Claude Code (work)84% leftClaude Code (work)77% left
- Grok62% left
- Codex (side)52% left
The full version follows this task further: how PugPort judges a task’s difficulty, what goes into the handoff note, and how the next account checks it before carrying on.