Total spend (live)
selected window
Financial command
Live operational oversight for agent spend, model routing, task cost, and cheap-lane leakage. This surface is tuned for fast diagnosis, forecasting, and intervention.
Powered by Nexus sub-agent execution telemetry. Historical runs without token fields under-report cost; newer runs are more reliable.
Total spend (live)
selected window
Daily trend
vs previous hour
trendWeekly burn rate
current run rate
Avg cost / task
execution average
Cost anomaly
last hour spend
Top spending agent
0% of selected spend
Top spending model
0% of selected spend
Most expensive task
Leakage score 0/10
Leakage overview
0 high-risk leakage sources
Cost timeline
Tier classification
0% of spend
0% of spend
0% of spend
Model family
No model-family cost data yet.
Forensics
| Agent | Tasks | Runtime | Tokens | Cost | Avg Task | Cost / 1k | Actions |
|---|
Forensics
| Model | Family | In | Out | Total | Cost | Cost / 1k |
|---|
Operational leakage
| Task | Agent | Model | Runtime | Tokens | Cost | Leakage | Actions |
|---|
Signal
Signal
Signal
Document 1 / 3
This page now reflects the current Nexus build honestly: what exists in the repo, what is still missing, and which observability upgrades make sense next.
EMBER jobs
0 active
Research success
12 success
Saved briefs
12 persisted
Avg confidence
heuristic confidence
Avg duration
0 escalated
Live now
This Nexus surface is a real Next.js page in the current portal build and ships as part of the existing UI.
The repo currently uses Prisma with a local SQLite database for portal state in this build.
A small amount of operational automation exists today, including milestone forwarding and deadline watching scripts.
Reality check
Recommended next layer
Keep this page grounded in what is actually shipped. Separate live capabilities from recommended next steps.
Add health checks, structured logs, key counters, and a small internal status board before adopting a full observability stack.
Wire alert thresholds to real failure conditions such as portal downtime, queue stalls, repeated task failures, or deadline misses.
Introduce CI for lint and build, then controlled deployment automation once release steps are stable.
Only add Prometheus, Grafana, Loki, or Terraform once the operating model and team response flow are real requirements.
Reference only
Good future choice if Nexus needs durable scrape-based metrics and alert rules.
Useful when logs need central search, retention, and drill-down during incidents.
Helpful once live metrics and logs exist and operators need one review surface.
Worth adding after thresholds, ownership, and escalation routes are clearly defined.
These tools are recommendations, not evidence that the current Nexus deployment already runs them.