aiqbench analysis
This research dissects the Option-Critic algorithm, revealing that its standard performance gains stem from redundancy rather than superior sub-policies. The authors identify "policy necrosis," where internal policies fail to explore and lock onto initial actions, while showing that forcing frequent termination eliminates this issue without altering the option count curve. Ultimately, the study demonstrates that adding more options only improves robustness by reducing the probability of simultaneous failure across all options, rather than enhancing individual policy quality.
When Do Options Help? Policy Necrosis and Redundant Coverage in Option-Critic
arXiv:2609.05508v1 Announce Type: new Abstract: Option-critic learns options: sub-policies together with a learned rule for when each one hands control back. Its headline result is that performance improves as options are added. We explain that result, with theory and experiment. First, the termination rule option-critic learns by maximising return contributes nothing. When the termination test and the policy that picks options read the same values, the test fires at every step, so the learned rule is identical to always terminating. When that policy explores and the test does not, as in option-critic itself, the rule can block the exploration; there are instances where it suffers $\Omega(T)$ regret while always terminating holds to $O(\log T)$. Forcing termination at every step leaves the option-count curve intact. Second, the policy inside an option barely explores at all, so a state locks onto the first action that looked good and never updates again. We name this policy necrosis, give a state-level test for it, and find three fifths of states necrotic in a typical option. Restoring exploration repairs those states, and one option then solves the task. Third, extra options improve no option; what falls is the chance that all of them fail in the same state, from $59\\%$ to $4\\%$, and performance follows that joint quantity.
Title:When Do Options Help? Policy Necrosis and Redundant Coverage in Option-Critic
Abstract:Option-critic learns options: sub-policies together with a learned rule for when each one hands control back. Its headline result is that performance improves as options are added. We explain that result, with theory and experiment. First, the termination rule option-critic learns by maximising return contributes nothing. When the termination test and the policy that picks options read the same values, the test fires at every step, so the learned rule is identical to always terminating. When that policy explores and the test does not, as in option-critic itself, the rule can block the exploration; there are instances where it suffers $\Omega(T)$ regret while always terminating holds to $O(\log T)$. Forcing termination at every step leaves the option-count curve intact. Second, the policy inside an option barely explores at all, so a state locks onto the first action that looked good and never updates again. We name this policy necrosis, give a state-level test for it, and find three fifths of states necrotic in a typical option. Restoring exploration repairs those states, and one option then solves the task. Third, extra options improve no option; what falls is the chance that all of them fail in the same state, from $59\\%$ to $4\\%$, and performance follows that joint quantity.
Machine Learning (cs.LG); Artificial Intelligence (cs.AI)
arXiv:2609.05508 [cs.LG]
(or arXiv:2609.05508v1 [cs.LG] for this version)
https://doi.org/10.48550/arXiv.2609.05508 Focus to learn more arXiv-issued DOI via DataCite (pending registration)
arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.
Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.
Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.
Full text under the publisher's open licence · 316 words
Related coverage

How Cohere Health digitizes clinical policies using Amazon Bedrock AgentCore
AWS · Aug 7, 2026
The current bottleneck is political will, not research
AI Alignment Forum · Jul 11, 2026
Nemotron 3.5 Content Safety: Customizable Multimodal Safety for Global Enterprise AI
Hugging Face · Jun 4, 2026
.webp%3Fssl%3D1&w=320)
Top 50 Best Penetration Testing Companies in 2026
Cybersecurity News · Jul 31, 2026