WeSearch

Orca-Bench: How Ready Are Language Model Agents for Oncall?

·3 min read · 0 reactions · 0 comments · 3 views
#orca-bench#ready#language#model#agents
Orca-Bench: How Ready Are Language Model Agents for Oncall?
TL;DR · WeSearch summary

Computer Science > Computation and Language arXiv:2607.28545 (cs) [Submitted on 30 Jul 2026] Title:ORCA-bench: How Ready Are Language Model Agents for Oncall? We introduce ORCA-bench, a benchmark that puts general-purpose coding agents in a production-fidelity oncall setting. Ground-truth symptoms are curated and signed off by expert SREs, and our LLM-as-judge is independently re-scored by humans (Cohen's $\kappa_w=0.90$).

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 899 of its stories. Top-voted stories on Hacker News.

Original article
arXiv.org
Read full at arXiv.org →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherarXiv.org
Canonical URLhttps://arxiv.org/abs/2607.28545
Publication timeFri, 31 Jul 2026 18:32:43 +0000
Retrieval time2026-07-31T19:14:02.657Z
Last seen2026-07-31T19:14:02.657Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clustervt-qkl_Dejj1 · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Computer Science > Computation and Language arXiv:2607.28545 (cs) [Submitted on 30 Jul 2026] Title:ORCA-bench: How Ready Are Language Model Agents for Oncall? Authors:Albert Gong, Kyuseong Choi, Abhineet Agarwal, Jason Schechner, Ryan Huang, Raj Agrawal, Anish Agarwal, Raaz Dwivedi View a PDF of the paper titled ORCA-bench: How Ready Are Language Model Agents for Oncall?, by Albert Gong and 7 other authors View PDF HTML (experimental) Abstract:Large language models can write, patch, and search code, but oncall root cause analysis (RCA) demands something different: reasoning over noisy metrics, logs, traces, and source code, starting from ambiguous user-facing reports, often hours after the incident began.

Excerpt limited to ~120 words for fair-use compliance. The full article is at arXiv.org.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from arXiv.org