- Rating
- 2(+1)
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper introduces CBM-Scientist, which is an agentic framework to automatically improve concept bottleneck models (CBMs). The framework employs an agent to iteratively refine training or model architecture choices of a CBM. Thereby, the agent can modify and evaluate the base CBM and, based on the history of previous exploration and guided by several given target metrics, tries to optimize the smaller details of the CBM structure/training.
Critical strengths
- The paper proposes an agentic framework to modify a given CBM architecture under certain constraints (e.g., only modifying parts of the model), which can improve the downstream performance of the CBM by optimizing its engineering.
Critical weaknesses
- While the main idea of using agentic frameworks to automatically construct/improve CBMs is promising, the execution in this paper falls short of what automatic construction should mean in the context of CBMs (and what is claimed in the paper's contributions). There are well-established modules and parts of the CBM pipeline which have important consequences on the way a CBM is set up and works. However, combining these different aspects can be challenging and requires experimentation. But instead of leveraging the knowledge pool that the CBM field has built over the years, the automatic changes in this paper mainly result in small architectural engineering changes, which are mostly not specific to CBMs.
- The experimental evaluations and setups of the paper lack consistency and are partially insufficient to properly evaluate the introduced method. Some parts of the evaluation are apparently unfinished, and the paper just contains partial results.
Questions for authors
In the following, I have collected several important points/questions regarding the paper, which I would appreciate the authors responding to/clarifying during the rebuttal.
Q1: There are several different agentic approaches introduced, with different performance, but the differences between these agents is never systematically evaluated or discussed. Can the authors comment/discuss why the agents perform differently, and what systematic differences between agentic strategies were?
- In addition to that, Appendix D.1 even introduces two more variants which are partially evaluated on a part of the datasets, but their performance and implications are never discussed.
Q2: In any automatic setting, it is important to compare cost and benefit, which is not done in this work. There is no discussion on how long this agentic loop should be run. The prompt at the end states it should run until interruption, but stopping criteria are never mentioned/discussed in the paper. Can the authors please discuss the duration of the agentic loop and its connection to performance, in particular regarding the multi-target setting?
Q3: Experimental Evaluation is apparently not finished:
- Several results in the appendix are missing seeds, or are just outright missing runs.
- Line 1256 even states, "These are development results, not held-out test results"
- There are comparisons to other Agents (DeepSeek and Claude Opus, but they are not done on the main experiment results/with the same base CBM configurations, but instead with a different configuration) Q4: Discussion of computational cost of the paper is insufficient:
- For the estimated costs, the authors report the average cost per candidate in the different settings, but it is unclear how many candidates have been used. Further, for GLM, the authors should, if possible, report the estimated number of GPU-hours and the total number of candidate rounds as well
- What does it mean that the costs are only computed over completed, scored candidates? Q5: The agents are restricted from changing specific parts of the model and should not change the evaluation setting, but this is only done via prompt. As there are known cases of LLMs doing reward hacking/monkey patching of evaluation functions [1], did this happen during the runs? Q6: Can the authors please position their paper with regard to the field of AutoML? [2] Q7: It is unclear what reported standard deviations are over (l.359 does not state this), and then there is an explicit (and maybe different) standard deviation evaluation in Tab 4. Can the authors please clarify this?
Q8: There is a lot of work on CBMs that introduces different modifications to part of the CBM architecture. Over the years, many different ideas to handle concept annotations, interpretable prediction, input encoding, ... have been proposed. Furthermore, the design space of CBMs has for example been explicitly discussed in [3]. An agentic framework to construct and adapt CBMs should make use of this work. This could, for example, be done by giving the Agents more explicit access to this design space and more freedom to explore it. Additionally, having access to the data and using the data characteristics explicitly to inform the methodological decisions could be helpful there. Can the authors please discuss the current approach in this context?
Q9: In the full experimental evaluation, the results sections just describe the results shown in the tables, but there is no discussion/interpretation of these results given at all. The written text does not have much benefit besides the tables, and compiling more meaningful insights (i.e. why the agentic systems perform better, what changes they made, and what differences there are between the different agentic setups), should be more discussed in the main paper.
Q10: Given that one of the main focus points of CBMs is their interpretability, did the authors perform any investigations into the interpretability of the resulting models, and how it changed compared to the baselines? Also, how many of the changes the agents made were helping/hindering interpretability in general (e.g., as adding more bypass capacity reduces interpretability, improving disentanglement/discretization helps interpretability, ...)?
Q10: There is no Discussion of limitations at all. It would be important to discuss, for example, cost-efficiency, the search space of the agents and proposed changes, the importance of the evaluation criteria, and the lack of interpretation evaluation.
Minor things:
- Tab 9: Comparing VHCB and the baseline (and the Agents trained on VHCB) is a bit weird, because the latter has a different architecture and setting. From the results, it is not even clear whether VHCB is even better than the baseline.
- Sec. 4.3: why are the headers called image classification and then the model names for the other two paragraphs? Furthermore, why are sprint internal numbers used in the last paragraph, but not in all the other paragraphs?
[1] Baker, Bowen, et al. "Monitoring reasoning models for misbehavior and the risks of promoting obfuscation." arXiv preprint arXiv:2503.11926 (2025). [2] Zöller, Marc-André, and Marco F. Huber. "Benchmark and survey of automated machine learning frameworks." Journal of artificial intelligence research 70 (2021): 409-472. [3] Knab, Patrick, et al. "What’s in the bottle? a survey and roadmap of concept bottleneck models." Transactions on Machine Learning Research (2026).
10 comments
Rebuttal (2/4)
Q3: Completed results and evaluation splits
A3: We would like to clarify that all results in the main submission were complete. In the appendix, we included some extra settings whose results were incomplete at the time of submission. We have now completed them, so in total we have nine settings across three model families (Tables 2 and 3, Section 4, and Tables 14 and 15, Appendix E.1).
-
L1256 : “These are development results, not held-out test results”: This was referring to the GSM8k validation set. (Table 8, Appendix D.2.2). We have completed the experiments and have reported the results on the held out test set in Table 15 (Appendix E.1).
-
We extended the results with DeepSeek and Opus agents on a few settings with Image Generation (Table 9, Appendix D.2). In the one setting we evaluated, a stronger agent (Opus 5) gave better results, which suggests that performance may improve with stronger agents, at a higher API cost (Opus 5 token costs are 2.5× those of Sonnet 5). Testing this more broadly remains future work.
-
We also explored some more agent orchestration variants on limited examples (Figure 4, Table 6, Appendix D.1). We find early experimentation didn’t lead to any significant improvements. We also don’t find any consistent improvement of using supervisor (which is a multi agent framework) over the single agent variants (self-directed , loss, arch ) (Fig 2). Systematic study of different agent orchestrations on CBM Research remains an open question.
Q4: Computational budget and estimated costs
A4: Tables 18–20 (Appendix E.1) now report the number of candidates and the estimated API cost for every sprint, as totals and per candidate. Across datasets, Claude Sonnet 5 sprints produced 3,777 candidates at an estimated USD 8,597.52, and GLM 5.3 sprints produced 2,928 candidates at an estimated USD 6,126.19. These are API-equivalent estimates from published prices: we used a USD 200 Claude Max subscription, and GLM 5.3 was served by an external provider at no charge, so the two should not be compared directly.
completed, scored candidates ?
We are referring to the total number of candidates with a metric score. We agree that is confusing and we will fix this in the revised version.
Q5: Reward hacking and exclusion of affected results
A5: Yes, in two sprints, both run by GLM 5.3. None of the scores from the affected runs were used in our reported results.
- AGNews text generation (self-directed). Starting with candidate #59, the agent queried the steering classifier during generation and used its score to decide whether to keep generating or to retry an output. The evaluator file stayed unchanged, but its feedback shaped the text it scored. We report candidate #54, which predates this change.
- CUB image generation (architecture-constrained). The agent used the classifiers that score steerability to choose how to edit each concept. In a separate trial, it tuned the concept predictor's biases against the same classifiers after training.
Q6: Relationship to AutoML
A6: AutoML, surveyed by Zöller and Huber (2021) [2], shares our goal of automating model design but searches over a predefined space of pipelines, algorithms, and hyperparameters. We instead let an LLM agent propose, implement, and evaluate code changes to a CBM, drawing on ideas from other areas of machine learning, combining them, and refining them from feedback. Starting from established CBM baselines, agents improved several objectives together. Most proposals are standard changes (Table 21, Appendix E.2), but agents also proposed four ideas that, to the best of our knowledge, have not been applied to CBMs before, such as a Fourier loss that keeps a concept-edited image close to the original and concept scores that gate the unsupervised features of a generative CB-LLM (Appendix E.3, Table 22).
Q7: Sources of variation in the reported results
A7: In Tables 1–3, 14, and 15, we train the same selected recipe with three random seeds, so the SD measures variation between training runs. In Table 4, we repeat the whole sprint three times. Each sprint can select a different recipe, so the SD measures variation across sprints. We will state this in each caption.
Rebuttal (3/4)
Q8: Exploration of the CBM design space
A8: In Appendix E.3 (Table 22), we classify the agents' changes by where they enter the CBM pipeline, following the design space of Knab et al. (2026) [3]. Below, we explain how our setup and the agents' changes relate to its design choices:
-
Concept annotations. We fixed the concept vocabulary and source annotations within each sprint. The agents could still change how they used them during training: for example, an ImageNet agent softened zero targets according to the concept predictor’s own confidence (Appendix E.3, 1(iii), “Confidence-based soft labels”).
-
Interpretable prediction. Following VLG-CBM’s evaluation protocol, each candidate’s concept predictor is frozen and a fresh sparse classifier is fitted at the same budget, so the sparse classifier is fixed. This did not stop a CUB agent from training a temporary classifier on partly corrected concepts to make the concept head more intervenable (Appendix E.3, 1(iv), “Intervention-aware training”).
-
Interpretable generation. In CB-AE or CB-LLM, unlike in VLG-CBM, the decoder and unsupervised pathways are not fixed, and agents could modify them where their strategy allowed. An SST2 agent used the predicted concept scores to gate each unsupervised feature before it reached the decoder (Appendix E.3, 2a(iii), “Gate unsupervised features”). For image generation, a CelebA-HQ agent mapped each concept’s scores to an embedding and appended these embeddings to the decoder input (Appendix E.3, 3(iii), “Per-concept decoder inputs”).
-
Input encoding. Agents could change how backbone features were mapped to concepts. On AGNews, an agent concatenated the current token’s hidden state with the mean of all hidden states through that token (Appendix E.3, 2a(i), “Context-pooled concept head”). In image classification, agents modified the concept predictor in other ways, such as a gated nonlinear residual head (1(i)) and pairwise feature interactions (1(ii)).
Q9: Interpreting the experimental findings
A9: The main paper discusses the results in Sections 4.3 (recurring ideas and their outcomes) and 4.4 (a case study). To add interpretation, we include in the new Appendix E: a comparison of the held-out and original results (Tables 14–16, Appendix E.1), patterns across proposal strategies (Table 21, Appendix E.2), the measured effect of each design choice and case studies of individual agent decisions (Table 22, Appendix E.3), and an extended discussion (Appendix E.4). We will move the important findings into the main paper after the rebuttal.
Q10: Evaluating concept prediction and intervention
A10: We evaluated two aspects of interpretability: how accurately the model predicts the annotated concepts, and how its output responds when those concepts are edited. Across the 56 sprints that measured both, 47 selected recipes improved both mean concept prediction and the intervention metric over their respective baselines (Tables 2, 14, and 15). The remaining 16 image-generation sprints measured steerability without a separate concept-prediction score. All 16 selected recipes improved mean steerability over baseline (Table 3).
The reviewer’s concern about bypassing the bottleneck is visible in the CUB image-generation sprint. An agent gave the decoder a path that carried information about image style through unsupervised features. Adding this path improved reconstruction FID from 68.10 to 9.20, but steerability decreased from 17.12% to 2.08%. Reducing the path to one-quarter strength brought steerability back to 10.50%, while reconstruction FID worsened to 55.27 (Appendix E.3, 3(ii)). The decoder could reconstruct images more faithfully through this path, but edits to the named concepts had less influence on the output.
Rebuttal (1/4)
We thank the reviewer for the detailed feedback. As described in the global response, in the new Appendix E, we add experiments and analyses that address many of the points raised. Based on the feedback, we also position our work with respect to the CBM design space of Knab et al. (2026) [3]: in Appendix E.3 (Table 22), we organize the changes the agents made by where they enter the CBM pipeline. We address all of the concerns one by one.
W1: CBM-specific adaptations and connections to prior work
We agree that most proposals are standard changes (76.3% of the 6,650 across the 72 sprints; Table 21, Appendix E.2). This is expected when an agent starts from an existing CBM. But the agents also use what the CBM field already knows: some reuse known CBM techniques, and 14.0% are CBM-specific changes tailored to concept prediction, concept use, or intervention. These changes are not trivial. They span the modules of the CBM taxonomy of Knab et al. (2026), and from them we identify four ideas that, to the best of our knowledge, have not been applied to CBMs before (Appendix E.3, Table 22; Global Response, point 3). We discuss how the agents work within the CBM design space in Q8.
W2: Evaluation completeness and consistency
We agree that parts of the appendix were incomplete at submission, although all results in the main paper were complete. We have now completed the evaluation in two ways. First, four settings (CUB, ImageNet, AGNews, SST2) used test-set feedback during the sprints, so we reran them with validation feedback only and evaluated the selected recipes on a separate held-out test set, as described in the Global Response. Second, we completed the two remaining settings, GSM8K and CUB with human-annotated attributes (the original CBM of Koh et al. (2020)). All reruns use three training seeds (Tables 14 and 15, Appendix E.1). In total, the evaluation covers 72 sprints: 48 are the reruns in Tables 14 and 15, and the other 24, on FinQA and image generation, did not use test-set feedback and are in Tables 2 and 3. We address the specific incomplete results in Q3.
Q1: Comparing proposal strategies across settings
A1: We have expanded the analysis in Appendix E.1 and E.2. Across the nine settings, no single proposal strategy performed best in all of them. In Appendix E.2, we also classify every candidate by its main change, for example as a standard change or a CBM-specific adaptation (a change tailored to concept prediction, concept use, or intervention).
We observe that loss- and architecture-constrained sprints were more likely than self-directed and supervisor sprints to propose CBM-specific adaptations in every model family. All four ideas that, to the best of our knowledge, have not been applied to CBMs before (Appendix E.3, Table 22) also came from these sprints. This does not mean that they performed best. The best-performing recipes often came from other strategies, and which strategy worked best depended on the dataset and metric. We discuss the two additional agent variants of Appendix D.1 in Q3.
Q2: Search duration, stopping criteria, and additional gains
A2: We set a budget of about 100 candidates per sprint and instructed the agent to continue until interrupted. Some sprints ended earlier when the agent stopped proposing changes or repeated failures blocked progress. Others ran slightly longer. We did not use a convergence-based stopping rule.
We reviewed all 24 image-classification sprints and all 16 text-generation sprints. Table R3 shows the results. At each cutoff, we scored the best recipe seen so far using the paper’s standard selection weights. If a sprint ended before a cutoff, we carried its best score forward.
Table R3: Best weighted gain over baseline by candidate budget. Δ denotes the recipe score minus baseline for each metric. Rates use a 0–1 scale. Classification = 100 × (0.5 Δaccuracy + 0.25 Δconcept AP + 0.25 Δintervention accuracy). Text generation = 100 × (Δconcept F1 + Δsteerability − 0.005 Δperplexity).
Stopping at 25 candidates would have missed a better recipe by candidate 50 in 20 of 24 classification sprints and 11 of 16 text-generation sprints. The benefit of continuing differed by task. Classification improved more gradually after candidate 25, while text generation still gained substantially between candidates 50 and 75. These results show what earlier stopping would have missed in the recorded sprints.