Thrum

What is talagentd, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job, man page and Desktop & Dock labels checked on macOS 26.3.1.

talagentd is the macOS helper agent for application lifecycle features, which its man page calls Transparent App Lifecycle. Its launchd job provides AppKit's storage for window restoration, the feature that reopens an app's windows the way you left them. It normally uses very little CPU.

talagentd at a glance

talagentd
Made byApple (part of macOS, AppKit)
TypeLaunch agent
Location/System/Library/CoreServices/talagentd
Runs asyour user
Started bylaunchd job com.apple.talagent
Can you quit it?Yes. launchd starts it again when apps save or restore window state.

What is talagentd?

Its man page describes talagentd as the helper agent for application lifecycle features, providing services related to Transparent App Lifecycle, and says users should not run it manually. Its launchd job offers services named com.apple.appkit.restoration_storage and com.apple.window_proxies. Restoration is the AppKit feature where an app, when it opens, recreates the windows that were open when it last quit.

Whether windows come back is controlled by Close windows when quitting an application in System Settings > Desktop & Dock. launchd starts talagentd for your user on demand, and its job is also scheduled to run at 3:00 on Mondays and Thursdays.

Is talagentd safe?

Yes. talagentd is part of macOS, signed by Apple, and stored in /System/Library/CoreServices on the read-only system volume. It runs as your user.

Why does talagentd use so much CPU?

How much CPU is normal for talagentd?

At or near 0% CPU, often not running. Short activity when apps quit, open or save their window state is typical.

Memory use is typically in the tens of megabytes or less.

What can you do if talagentd keeps using CPU?

  1. Turn window restoration off. Open System Settings > Desktop & Dock and turn on Close windows when quitting an application. Apps then open without restoring old windows, so less state is saved.
  2. Close windows you no longer need. Apps with hundreds of open windows or tabs save more state each time; closing them reduces the work.
  3. Quit it once. If it stays busy, quit talagentd in Activity Monitor. launchd starts it again when needed.

When should you worry about talagentd?

Look closer if talagentd stays above a few percent CPU for many minutes. One app saving its state in a loop is the likely cause; quitting apps one by one finds it.

It should run only from /System/Library/CoreServices/talagentd.

How do you check talagentd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type talagentd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every talagentd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'talagentd' | grep -v grep

How can Thrum help with talagentd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when talagentd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click talagentd in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about talagentd

What does Transparent App Lifecycle mean?

It is Apple's name, in the talagentd man page, for app lifecycle features such as restoring an app's windows when it reopens.

Why does talagentd run at night?

Its launchd job is scheduled to run at 3:00 on Mondays and Thursdays, in addition to running when apps need it.

Sources