[codex] add diagnostics resource history

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Just a quick way to get some intel... might need to be a separate binary later that uses platform specific native APIS

Summary

Adds an in-memory process resource monitor for Diagnostics that samples the T3 server root process and live descendants over time. The new history API rolls samples up into CPU-time summaries and chart buckets so the UI can show cumulative CPU, current/average/peak CPU, and memory peaks across selectable windows.

Details

• Adds a ProcessResourceMonitor service with a bounded 60-minute in-memory ring buffer.
• Includes the root T3 server process in the sampled state alongside descendants.
• Adds server.getProcessResourceHistory contracts/RPC/client wiring.
• Extends Settings -> Diagnostics with a Resource History section, window selector, CPU timeline, and top process table.
• Keeps existing live process diagnostics and process signaling behavior unchanged.

Validation

• bun fmt
• bun typecheck
• bun lint (passes with existing warnings)
• bun run test src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts from apps/server

Note

Add process resource history to the diagnostics settings panel

• Introduces ProcessResourceMonitor (ProcessResourceMonitor.ts) that samples server process metrics every 5s, retaining a rolling window of results, and exposes a readHistory method returning bucketed CPU/memory aggregates per process.
• Adds a server.getProcessResourceHistory RPC (rpc.ts) with full schema definitions for input, per-bucket metrics, per-process summaries, and the result envelope.
• The diagnostics settings UI (DiagnosticsSettings.tsx) gains a selectable time window (5m/15m/30m/1h), a stacked CPU bar chart, a process summary table, and total CPU seconds stats.
• Client-side state uses an Atom.family keyed by window/bucket sizes for SWR-style caching and refresh via useProcessResourceHistory.

^{Macroscope summarized 7b5ab2f.}

---

Note

Medium Risk
Adds a new background sampler that periodically shells out to read process stats and retains in-memory history, plus a new RPC endpoint and UI surface; main risk is performance/memory overhead and correctness of aggregation across platforms.

Overview
Adds a new ProcessResourceMonitor service that samples the server root process plus live descendants every 5s, retains a bounded in-memory history, and aggregates samples into per-process CPU-time/memory summaries and time buckets.

Wires a new server.getProcessResourceHistory WebSocket RPC end-to-end (contracts, server handler, client/local API, and atom-based caching) and disables tracing for it alongside other diagnostics RPCs.

Extends Settings → Diagnostics with a Resource History section (window selector, CPU timeline chart, and top-process table) and makes small usability tweaks to the existing Live Processes table (sticky header, tooltip for full command, adjusted indentation/scrolling).

^{Reviewed by Cursor Bugbot for commit 7b5ab2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 17bbb55f-e22b-458b-9177-e4ff1d71793f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/better-diagnostics-monitoring

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Redundant fetch logic diverges between refresh and interval
  • Replaced the duplicated fetch logic in the refresh callback with a refreshKey state counter that triggers the useEffect to re-run, ensuring a single fetch path with isMounted guards and proper interval reset.

Or push these changes by commenting:

@cursor push 842ce7848e

Preview (842ce7848e)

diff --git a/apps/web/src/lib/processDiagnosticsState.ts b/apps/web/src/lib/processDiagnosticsState.ts--- a/apps/web/src/lib/processDiagnosticsState.ts+++ b/apps/web/src/lib/processDiagnosticsState.ts@@ -83,22 +83,11 @@
const [data, setData] = useState<ServerProcessResourceHistoryResult | null>(null);
const [error, setError] = useState<string | null>(null);
const [isPending, setIsPending] = useState(true);
+ const [refreshKey, setRefreshKey] = useState(0);
const refresh = useCallback(() => {
- setIsPending(true);- void ensureLocalApi()- .server.getProcessResourceHistory({ bucketMs, windowMs })- .then((result) => {- setData(result);- setError(null);- })- .catch((cause: unknown) => {- setError(formatProcessDiagnosticsError(cause));- })- .finally(() => {- setIsPending(false);- });- }, [bucketMs, windowMs]);+ setRefreshKey((k) => k + 1);+ }, []);
useEffect(() => {
let isMounted = true;
@@ -127,7 +116,7 @@
isMounted = false;
window.clearInterval(interval);
};
- }, [bucketMs, windowMs]);+ }, [bucketMs, windowMs, refreshKey]);
return { data, error, isPending, refresh };
}

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 20a2a1c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a complete new feature with a background process sampling system, new API endpoints, and new UI components for resource history visualization. New features of this scope warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}