Keep your Agents running

It watches every Agent on your computer. You just hand out the work

Download See pricing

looptend floating ball form: the open dial with five rings for Claude, Codex, cost, network and CPU

looptend workspace Overview: Performance CPU 34%, GPU 11%, Stable; live network chart; three Claude sessions Working in the Live Agents list: Fix login redirect, Finish payment callback tests, Write this week's release notes

Your turn Just now

Fix login redirect · my-app

Got itOpen session

Codex · Accounts

Switch automatically when quota runs out

Next session on the backup account

Floating ball

Claude
Codex
Antigravity
Grok
Cursor
GLM
MiniMax
WorkBuddy
Kimi
Claude
Codex
Antigravity
Grok
Cursor
GLM
MiniMax
WorkBuddy
Kimi

Why looptend

Claude
Codex
Antigravity
Grok
Cursor
GLM
MiniMax
WorkBuddy
Kimi

Current SessionsAgents & usageAccounts

4 sessions

Fix login redirectmy-app / web Working 1 min ago
Finish payment callback testsmy-app / payments Your turn just now
Tidy this week's release notesmy-app / docs Waiting for tool 3 min ago
Split home page componentsmy-app / web Turn complete 8 min ago

Your turnjust now

Finish payment callback tests

my-app / payments

Got itOpen session

Live monitorDeep network check

Codex

Claude

Connected, but Codex timed out fetching the model list

Local network
Proxy
DNS
Server
Realtime channel
Sign-in
Quota
Service status

How to fix

Switch to a US, Japan or Singapore node in Clash Verge and re-run the check

Codex left 6 helper process groups · 793 MB

Usage reportWork summary

TodayGenerate

Done today

Fixed the login redirect and added a regression test
Finished payment callback tests, refund branch covered
Tidied this week's release notes

ExportImageWordPDF

Token

2.49B

Est. cost

US$2,021

Codex 59%

Claude 41%

One stall, two waits

Without looptend

TerminalFileEditViewShellWindowHelp Wed 14:02

Codex

Add tests for the checkout retry logic, run them, then commit

Added tests/checkout/retry.test.ts covering timeout, retry cap and fallback. Running the suite next.

Approval needed: run npm testApproveDeny

github.com/acme/checkout-web/pull/128

Fix checkout retry #128npm test | npm Docs+

Fix checkout retry #128

tristan wants to merge 3 commits into main

lint · passed
unit · passed
e2e · running

tests/checkout/retry.test.ts+ it("retries on timeout", …)+ it("caps at three attempts", …)+ it("falls back after failure", …)

Product team

Sent you the new login mock, check the motion

Got it, merging this afternoon

Can the checkout retry bug ship today?

Claude is running tests, Codex has the other half

Great, give me status before the weekly

retry.ts — checkout-web

src
checkout
retry.ts
cart.ts
tests
retry.test.ts

export async function withRetry(fn, opts = {}) {
  const max = opts.max ?? 3;
  for (let i = 0; i < max; i++) {
    try { return await fn(); }
    catch (err) {
      if (!isTimeout(err) || i === max - 1) throw err;
      await sleep(200 * 2 ** i);
    }
  }
}

checkout-web — claude

✻ Welcome to Claude Code

/Users/you/dev/checkout-web

> add unit tests for the checkout retry logic

⏺ Read(src/checkout/retry.ts)

⏺ Write(tests/checkout/retry.test.ts)

└ 3 cases: retry on timeout, cap at 3, fall back after failure

⏺ Bash(npm test -- retry)

└ 3 passed, 0 failed (1.8s)

⏺ Edit(src/checkout/retry.ts)

└ use isTimeout() for the check, drop the duplicate catch

✳ Thinking… (esc to interrupt)

With looptend

TerminalFileEditViewShellWindowHelp Wed 14:02

Codex

Add tests for the checkout retry logic, run them, then commit

Added tests/checkout/retry.test.ts covering timeout, retry cap and fallback. Running the suite next.

Approval needed: run npm testApproveDeny

github.com/acme/checkout-web/pull/128

Fix checkout retry #128npm test | npm Docs+

Fix checkout retry #128

tristan wants to merge 3 commits into main

lint · passed
unit · passed
e2e · running

tests/checkout/retry.test.ts+ it("retries on timeout", …)+ it("caps at three attempts", …)+ it("falls back after failure", …)

Product team

Sent you the new login mock, check the motion

Got it, merging this afternoon

Can the checkout retry bug ship today?

Claude is running tests, Codex has the other half

Great, give me status before the weekly

retry.ts — checkout-web

src
checkout
retry.ts
cart.ts
tests
retry.test.ts

export async function withRetry(fn, opts = {}) {
  const max = opts.max ?? 3;
  for (let i = 0; i < max; i++) {
    try { return await fn(); }
    catch (err) {
      if (!isTimeout(err) || i === max - 1) throw err;
      await sleep(200 * 2 ** i);
    }
  }
}

checkout-web — claude

✻ Welcome to Claude Code

/Users/you/dev/checkout-web

> add unit tests for the checkout retry logic

⏺ Read(src/checkout/retry.ts)

⏺ Write(tests/checkout/retry.test.ts)

└ 3 cases: retry on timeout, cap at 3, fall back after failure

⏺ Bash(npm test -- retry)

└ 3 passed, 0 failed (1.8s)

⏺ Edit(src/checkout/retry.ts)

└ use isTimeout() for the check, drop the duplicate catch

✳ Thinking… (esc to interrupt)

When it stops, you know

It's waiting, you didn't seeYour turn, open the session

A standing your-turn badge on the top bar, sidebar and floating ball
The reminder card appears beside your form and never steals focus
Hit Open session and you're back in that session

BeforeSix windows, which one is waiting?NowThe bar lights up, one click back

Your turnjust now

Refactor the notifier modulenotifier

Got itOpen session

Your-turn alerts

Out of quota, offline, frozenFind the snag, know the fix

Checks the network link by link, names the broken one and the fix
Finds the processes slowing your computer and re-checks before ending them
One account runs dry, the next session switches to one with quota left Pro

BeforeGuessing: network or quota?NowOne verdict, one fix

Live monitorDeep checkStart check

1 issue found

Codex

Connected, but Codex timed out fetching its model listRequests to OpenAI stall or fail; the proxy node is slow or unstable

Local network
Proxy
DNS
Server
Realtime
Login
Quota
Service

How to fix

Switch to a US, Japan or Singapore node in Clash Verge

Open Clash VergeRun again

Switch automatically when quota runs out

Current PRO

Backup PRONext session

Codex left 6 helper processes · 793 MB Deep check & accounts

Report due, bill unreadOne click, all laid out

See tokens and estimated cost by Agent, project and model
Press Generate for a first-person work summary
Export as image, Word or PDF

BeforeWeekly reports from memoryNowOne click and it's written

looptendWork summarySep 27, 2026

Done today

Fixed the login-page redirect; the regression suite passes
Completed payment-callback tests, covering refunds and duplicate notices
Wrote this week's release notes and shared them with the team

Claude

Codex3 sessions · 2 projects

Generate

Usage reportLast 7 days

Tokens: 1.86B
Est. cost: ≈ $1,480
Active days: 6
Peak day: 420M

Export

Save image
Word
PDF

Work summary & usage report

Your screen, your call

Display

Display formStatus & alerts

Display form

Quota

Style

Chart style

Your-turn alerts

Wk 90% Wk 1%

Tokens this year

9.59B

64%

36%

Fix login redirectmy-appWorkingjust nowOpen session

Finish payment callback testsshop-apiWorking1 min agoOpen session

Tidy release notesdocsTurn complete5 min agoOpen session

Claude

5 h51%

Weeklyresets in 34 min90%

Fix login redirectmy-app · just nowOpen session

Finish payment callback testsshop-api · 1 min agoOpen session

Tidy release notesdocs · 5 min agoOpen session

Codex

Weekly1%

No sessions for this agent right now

Running smoothlyPerformance

Room left to run agents

CPU34%

GPU11%

Memory pressure

Low

TransferringNetwork

Agents share the network with these transfers

Download204 Kbps

Upload3.1 Mbps

Latency42 ms

Peak in 30 s↓ 2.4 · ↑ 19.9 Mbps

InterfaceWi-Fi

Wk90%

Claude

5 h51%

Weeklyresets in 34 min90%

Fix login redirectmy-app · just nowOpen session

Finish payment callback testsshop-api · 1 min agoOpen session

Tidy release notesdocs · 5 min agoOpen session

Codex

Weekly1%

No sessions for this agent right now

Running smoothlyPerformance

Room left to run agents

CPU34%

GPU11%

Memory pressure

Low

TransferringNetwork

Agents share the network with these transfers

Download639 Kbps

Upload1.8 Mbps

Latency42 ms

Peak in 30 s↓ 2.4 · ↑ 19.9 Mbps

InterfaceWi-Fi

$Cost

Today≈ $11.80

Last 7 days≈ $86.40

Claude≈ $9.20

Codex≈ $2.60

Hand it off, come back on your turn

“Claude Code and Codex run side by side all day, and my AI bill is over two thousand dollars a month. I built looptend for myself first.”

— Tristan Tang · Founder, looptend
Claude Code and Codex openReply only on your turn
- One glance at the top bar: who's working, whose turn it is
- A card pops on your turn, one click opens the session
- A heads-up before quota runs low, no babysitting
Just got into flow, quota goneNext session, next account
- Multiple accounts: switch when quota runs out (Pro)
- Each account in its own official process, logins untouched
- Slow network? Deep check shows which link broke
“I burn through several accounts a month. Now when one runs dry, the next session just picks up another.”

— Independent developer
“I used to dig through an hour of session logs before the weekly meeting. Now it's one click and the week is written up.”

— Product manager, internet company
Digging through logs, againLet the summary write your week
- First-person work summary for any time range
- Usage report by Agent and project: what it cost
- Export as image, Word or PDF

Logins stay official,
data stays on your computer

looptend reads quota and status, nothing more. It never renews, copies or rewrites a login, and never signs in for you.

looptend Agents page: Subscription mode and API mode, with each Agent's accounts and quota

looptend Performance page: machine load, stable verdict, Agent process usage

looptend Reports page: work summary with the Generate button

Pricing

Free

US$0
- Nine Agents, sessions and status
- Your-turn alerts, Open session
- Live quota, network and computer
- Usage reports, weekly and monthly images
Download
Recommended
Pro

US$12/mo

US$96 a year
- Everything in Free
- Auto-switch accounts when quota runs out
- Deep network and performance checks
- Work summary, Word and PDF export
- Appearance: glass, display styles, running light
Download
Max

US$24/mo
- Everything in Pro
- Five or more accounts
- Several computers
- Long unattended Agent runs
Download

FAQ

Claude, Codex, Antigravity, Grok, Cursor, GLM, MiniMax, WorkBuddy and Kimi. You see sessions and status for every one of them; how deep quota reading and Open session go differs per Agent, and the app says so.

From local evidence on this computer: session files, processes and logs. When the evidence isn't enough it shows "No status" instead of guessing.

Free shows the quota of every account. With Pro and "Switch automatically when quota runs out" on, once an account is confirmed empty, the next session starts on an account that still has quota.

No. Logins are always held by the official processes; looptend only reads quota and status.

The deep network check tests link by link and tells you where it breaks and how to fix it; once fixed, run the check again. looptend never changes your proxy, DNS or VPN.

looptend Work: what everyone's Agents finished, confirmed by each person and written into daily and weekly reports, so the team aligns on work that actually got done. Priced per person.

See all questions

Give your Agents a keeper

Download

Your-turn reminder card with Got it and Open session buttons

looptend floating ball showing Claude week 94%

Keep your Agents running

Why looptend

One stall, two waits

Fix checkout retry #128

Fix checkout retry #128

When it stops, you know

It's waiting, you didn't seeYour turn, open the session

Out of quota, offline, frozenFind the snag, know the fix

Report due, bill unreadOne click, all laid out

Your screen, your call

Hand it off, come back on your turn

Claude Code and Codex openReply only on your turn

Just got into flow, quota goneNext session, next account

Digging through logs, againLet the summary write your week

Logins stay official,
data stays on your computer

Pricing

Free

Pro

Max

Standard

Custom

FAQ

Give your Agents a keeper

Keep your Agents running

Why looptend

One stall, two waits

When it stops, you know

It's waiting, you didn't seeYour turn, open the session

Out of quota, offline, frozenFind the snag, know the fix

Report due, bill unreadOne click, all laid out

Your screen, your call

Hand it off, come back on your turn

Claude Code and Codex openReply only on your turn

Just got into flow, quota goneNext session, next account

Digging through logs, againLet the summary write your week

Logins stay official,data stays on your computer

01 Only the official process holds your login

02 Status, quota and diagnostics are computed on your machine

03 A work summary is sent only when you press “Generate”

Pricing

Free

Pro

Max

Standard

Custom

FAQ

Which Agents does looptend support?

How does it know it's my turn?

What happens when my quota runs out?

Does looptend touch my accounts or logins?

Can it fix a slow network for me?

What is the team edition?

Give your Agents a keeper

Logins stay official,
data stays on your computer