Plastic Labs at ICLR 2026 Post#129
Merged
vintrocode merged 3 commits intov4from Mar 30, 2026
Merged
Conversation
WalkthroughAdded a new research announcement Markdown page announcing three Plastic Labs papers accepted to ICLR 2026: an RL/PPO adaptive test-time decoding policy, LogitScope for token-level uncertainty metrics, and SPIRAL, a zero-sum self-play method with role-conditioned advantage estimation (plus event logistics). Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
content/research/Plastic Labs at ICLR 2026.md (1)
99-99: Prefer internal wikilink for same-site content.Line 99 links to a Plastic Labs blog page via absolute URL. If the target exists in the content tree, use an Obsidian-style wikilink so internal navigation and SEO graphing remain consistent.
As per coding guidelines, "Link to other content using Obsidian-style wikilinks [[Page Title]]" and "Add internal links to aid navigation and SEO".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md at line 99, The link on the line containing "More details on this research can be found in this [blog post](https://blog.plasticlabs.ai/research/SPIRAL;-Letting-LLMs-Teach-Themselves-Through-Self-Play)." uses an absolute external URL; replace it with an Obsidian-style internal wikilink to the corresponding page in the content tree (e.g., [[SPIRAL: Letting LLMs Teach Themselves Through Self-Play]] or the exact internal note title) so internal navigation and SEO graphing work — locate that link text in the "Plastic Labs at ICLR 2026.md" document and update the markdown to use the wikilink form.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Line 42: The figure caption for "Figure 2" contains typos: change "aciheves"
to "achieves" and "repoted" to "reported" in the caption string for Figure 2 so
the sentence reads correctly (e.g., "RL achieves consistent improvements..." and
"Scores are reported..."); update only the caption text associated with Figure 2
to correct these spellings.
- Around line 23-50: Under the "Adaptive Decoding via Test-Time Policy Learning"
heading, split the narrative into explicit subsections titled "Methodology",
"Results", and "Conclusions": in Methodology describe the MDP formulation (agent
observes prompt, prefix, model logits, next-token entropy), the action space
(temperature, top-p), the PPO-trained policy and its architecture (2-layer MLP)
and any training/rollout details; in Results summarize evaluation metrics and
numbers reported (e.g., Granite-3.3-2B and Qwen-2.5-0.5B improvements, +88%
BookSum, +79% WikiHow), and note the ablation findings (ROUGE-only vs. shaped
rewards); in Conclusions state the core takeaways (adaptive decoding improves
over static heuristics, small models benefit, low compute overhead,
reversibility). Apply the same three-subsection structure to the other research
sections referenced in the comment.
- Around line 13-23: The document uses multiple top-level H1 headers; keep only
the single existing H1 (the title/frontmatter) and demote all other leading "#"
headings to proper H2/H3 levels — e.g., change "TL;DR", "We are at ICLR!",
"Adaptive Decoding via Test-Time Policy Learning" and the other section headings
referenced in the review to "##" (and any subsection headings to "###" as
needed) so the hierarchy is h1 → h2 → h3; update each heading token (the lines
starting with "#") accordingly throughout the file to restore a single top-level
heading and correct nested structure.
- Around line 28-30: Update all image references to use the relative ../assets/
path and replace Obsidian wikilink image syntax with standard Markdown: change
the inline Markdown images referencing iclr2026_sampler_diagram.png and
icrl2026_sampler_results.png to use ../assets/iclr2026_sampler_diagram.png and
../assets/icrl2026_sampler_results.png respectively, and convert any
Obsidian-style image links of the form ![[filename]] (seen for the images around
the content) into standard Markdown image links , ensuring alt text is descriptive for each image.
---
Nitpick comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Line 99: The link on the line containing "More details on this research can be
found in this [blog
post](https://blog.plasticlabs.ai/research/SPIRAL;-Letting-LLMs-Teach-Themselves-Through-Self-Play)."
uses an absolute external URL; replace it with an Obsidian-style internal
wikilink to the corresponding page in the content tree (e.g., [[SPIRAL: Letting
LLMs Teach Themselves Through Self-Play]] or the exact internal note title) so
internal navigation and SEO graphing work — locate that link text in the
"Plastic Labs at ICLR 2026.md" document and update the markdown to use the
wikilink form.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4a33dd25-c321-4573-9d9a-6d4471b4ccf4
⛔ Files ignored due to path filters (3)
content/assets/iclr2026_logitscope_ui.pngis excluded by!**/*.pngcontent/assets/iclr2026_sampler_diagram.pngis excluded by!**/*.pngcontent/assets/icrl2026_sampler_results.pngis excluded by!**/*.png
📒 Files selected for processing (1)
content/research/Plastic Labs at ICLR 2026.md
Deploying blog with
|
| Latest commit: |
0f12241
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b72725cc.plastic-labs-github-io.pages.dev |
| Branch Preview URL: | https://yuya-iclr-2026.plastic-labs-github-io.pages.dev |
There was a problem hiding this comment.
♻️ Duplicate comments (4)
content/research/Plastic Labs at ICLR 2026.md (4)
13-16:⚠️ Potential issue | 🟠 MajorUse a single top-level heading in body content.
Line 13 and subsequent section titles are still
#headings. Keep one H1 (title/frontmatter-driven) and demote section headings to##/###.Suggested heading-level fix
-# TL;DR +## TL;DR ... -# We are at ICLR! +## We are at ICLR! ... -# Adaptive Decoding via Test-Time Policy Learning +## Adaptive Decoding via Test-Time Policy Learning ... -# LogitScope: Analyzing LLM Uncertainty Through Information Metrics +## LogitScope: Analyzing LLM Uncertainty Through Information Metrics ... -# SPIRAL: Self-Play on Zero-Sum Games Incentivizes Reasoning +## SPIRAL: Self-Play on Zero-Sum Games Incentivizes Reasoning ... -# A Thread Running Through All Three +## A Thread Running Through All Three ... -# Find Us in Brazil +## Find Us in BrazilBased on learnings: Applies to content/**/*.md : Use clear, descriptive headings with proper levels (## and ###).
Also applies to: 23-23, 51-51, 80-80, 104-104, 112-112
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md around lines 13 - 16, The file uses multiple top-level '#' headings after the document title; change all subsequent H1 headings (e.g. "# TL;DR" and "# We are at ICLR!" and any other lines starting with a single '#') to appropriate lower levels (preferably "##" for primary sections or "###" for subsections) so only the frontmatter-driven title remains a single H1; update each occurrence of headings referenced in the review (the other '#' headings in the same file) accordingly.
42-42:⚠️ Potential issue | 🟡 MinorFix spelling typos in the Figure 2 caption.
Line 42 contains two typos:
aciheves→achieves,repoted→reported.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md at line 42, In the Figure 2 caption text ("*Figure 2: (Left) Main evaluation results with the Proposed Reward...*") correct the two typos: replace "aciheves" with "achieves" and "repoted" with "reported" so the sentence reads "RL achieves consistent improvements... Scores are reported...". Locate and edit the caption string accordingly.
23-50:⚠️ Potential issue | 🟠 MajorAdd explicit Methodology, Results, and Conclusions subsections per paper section.
For each research block (Adaptive Decoding, LogitScope, SPIRAL), add clear
### Methodology,### Results, and### Conclusionssubsections to match research-article structure requirements.Based on learnings: Applies to content/research/**/*.md : Include methodology, results, and conclusions sections in research articles.
Also applies to: 51-79, 80-103
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md around lines 23 - 50, This research block (the "Adaptive Decoding via Test-Time Policy Learning" section) is missing structured subsections; add explicit "### Methodology", "### Results", and "### Conclusions" subsections under that heading and similarly add those three subsections to the other research blocks referenced (LogitScope and SPIRAL) so each paper summary follows the research-article structure; place the Methodology paragraph to describe the MDP framing, observed state (prompt, prefix, logits, entropy), policy architecture (2-layer MLP) and PPO training, the Results paragraph to summarize quantitative gains (e.g., BookSum +88%, WikiHow +79%, cross-model robustness, ablation notes), and the Conclusions paragraph to state key takeaways (reward design importance, small-model benefits, deployment/reversibility of the policy).
28-30:⚠️ Potential issue | 🟠 MajorNormalize image references to relative
../assets/...Markdown paths.Line 30, Line 41, and Line 73 use bare filenames, and Line 85 uses Obsidian image syntax. Convert all image references to standard Markdown with relative asset paths.
Suggested image-reference fix
-](iclr2026_sampler_diagram.png) +](../assets/iclr2026_sampler_diagram.png) - + - + -![[selfplay.png]] +As per coding guidelines, "Reference assets with relative paths like ../assets/... from content sections".
Also applies to: 41-41, 73-73, 85-85
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md around lines 28 - 30, Replace all bare image references and Obsidian-style links in this document with standard Markdown image links pointing to the relative assets folder; e.g., change instances like "" and any other bare filenames or Obsidian syntax (![[...]] or similar) to "" (and likewise for the images referenced around the other image mentions), ensuring alt text is preserved and all image filenames are moved to ../assets/ and referenced via standard Markdown .
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Around line 13-16: The file uses multiple top-level '#' headings after the
document title; change all subsequent H1 headings (e.g. "# TL;DR" and "# We are
at ICLR!" and any other lines starting with a single '#') to appropriate lower
levels (preferably "##" for primary sections or "###" for subsections) so only
the frontmatter-driven title remains a single H1; update each occurrence of
headings referenced in the review (the other '#' headings in the same file)
accordingly.
- Line 42: In the Figure 2 caption text ("*Figure 2: (Left) Main evaluation
results with the Proposed Reward...*") correct the two typos: replace "aciheves"
with "achieves" and "repoted" with "reported" so the sentence reads "RL achieves
consistent improvements... Scores are reported...". Locate and edit the caption
string accordingly.
- Around line 23-50: This research block (the "Adaptive Decoding via Test-Time
Policy Learning" section) is missing structured subsections; add explicit "###
Methodology", "### Results", and "### Conclusions" subsections under that
heading and similarly add those three subsections to the other research blocks
referenced (LogitScope and SPIRAL) so each paper summary follows the
research-article structure; place the Methodology paragraph to describe the MDP
framing, observed state (prompt, prefix, logits, entropy), policy architecture
(2-layer MLP) and PPO training, the Results paragraph to summarize quantitative
gains (e.g., BookSum +88%, WikiHow +79%, cross-model robustness, ablation
notes), and the Conclusions paragraph to state key takeaways (reward design
importance, small-model benefits, deployment/reversibility of the policy).
- Around line 28-30: Replace all bare image references and Obsidian-style links
in this document with standard Markdown image links pointing to the relative
assets folder; e.g., change instances like "" and any other bare filenames or Obsidian
syntax (![[...]] or similar) to "" (and likewise for the images
referenced around the other image mentions), ensuring alt text is preserved and
all image filenames are moved to ../assets/ and referenced via standard Markdown
.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: fd3f8cd1-c18c-4fa8-9eb9-684294087698
📒 Files selected for processing (1)
content/research/Plastic Labs at ICLR 2026.md
vintrocode
requested changes
Mar 30, 2026
| Three papers with Plastic Labs authors were accepted at [ICLR 2026](https://iclr.cc/). One learns to control how a frozen LLM samples at test time. One gives you a window into what a model is actually uncertain about during generation. One trains reasoning capabilities from scratch using nothing but competitive self-play. We'll be in Brazil for the conference, so come by and chat with us! | ||
|
|
||
| # We are at ICLR! | ||
| Research is core to what we do at Plastic. The thesis behind [Honcho](https://honcho.dev/), that memory should be a reasoning task, not a storage task isn't just a product philosophy. It's a technical bet that serious machine learning can unlock genuinely new behavior from language models. |
There was a problem hiding this comment.
"the thesis [...] isn't just a product philosophy. It's a technical bet [...]" classic claude-ism, pls reframe
There was a problem hiding this comment.
also don't like calling these things bets, prefer theses
| # Find Us in Brazil | ||
| We'll be at ICLR in Brazil! If you're working on inference-time learning, post-training methods, uncertainty in language models, or memory and personalization for agents, we want to talk! | ||
|
|
||
| Come find us. |
There was a problem hiding this comment.
maybe we make this lower friction like "get in touch" with a typeform for us to get people's contact info / linkedin / twitter or something. could also link it at the top in the TLDR too
|
|
||
| The decoder sampler learns to control generation without retraining the LLM. LogitScope extracts uncertainty signals already present in the forward pass, no additional models required. SPIRAL builds reasoning from competitive dynamics alone, no problem sets needed. | ||
|
|
||
| That orientation matters to us because it maps directly onto the bets we're making at Plastic. Honcho's memory-as-reasoning thesis is fundamentally about what becomes possible when you stop treating language models as static artifacts and start treating inference as a site of active learning and adaptation. |
There was a problem hiding this comment.
maybe not "bets," rather "theses we hold" or something more scientific, less gambling-sounding
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
content/research/Plastic Labs at ICLR 2026.md (2)
30-32:⚠️ Potential issue | 🟠 MajorConvert image paths to use
../assets/relative path convention.Image references must follow the relative path convention from content sections. Line 32 references
iclr2026_sampler_diagram.pngdirectly instead of../assets/iclr2026_sampler_diagram.png.🔧 Proposed fix
- +As per coding guidelines, "Reference assets with relative paths like ../assets/... from content sections".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md around lines 30 - 32, Update the image reference string used in the markdown figure to follow the content-section asset convention: replace "iclr2026_sampler_diagram.png" with "../assets/iclr2026_sampler_diagram.png" in the markdown image tag (the line containing the Figure 1 image reference) so the file uses the required relative path; also scan the same paragraph for any other direct asset filenames and apply the same "../assets/..." convention to ensure consistency.
75-76:⚠️ Potential issue | 🟠 MajorConvert image path to use
../assets/relative path convention.Line 75 references
iclr2026_logitscope_ui.pngdirectly instead of using the required../assets/relative path.🔧 Proposed fix
- +As per coding guidelines, "Reference assets with relative paths like ../assets/... from content sections".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md around lines 75 - 76, Update the image reference to use the project's asset-relative path convention: replace the direct filename iclr2026_logitscope_ui.png in the content block (the Figure 3 markdown line) with ../assets/iclr2026_logitscope_ui.png so the asset is referenced as ../assets/iclr2026_logitscope_ui.png for correct resolution from the content section.
🧹 Nitpick comments (2)
content/research/Plastic Labs at ICLR 2026.md (2)
102-102: Consider using Obsidian wikilink syntax for internal blog reference.Line 102 links to an internal blog post using a full URL. Per the coding guidelines, internal content links should use Obsidian-style wikilinks for better maintainability.
♻️ Proposed improvement
-More details on this research can be found in this [blog post](https://blog.plasticlabs.ai/research/SPIRAL;-Letting-LLMs-Teach-Themselves-Through-Self-Play). +More details on this research can be found in this [[SPIRAL; Letting LLMs Teach Themselves Through Self-Play|blog post]].As per coding guidelines, "Link to other content using Obsidian-style wikilinks [[Page Title]]".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md at line 102, Replace the hardcoded external URL in the markdown link ("https://blog.plasticlabs.ai/research/SPIRAL;-Letting-LLMs-Teach-Themselves-Through-Self-Play") with an Obsidian-style wikilink to the internal blog page; update the link text in the "More details on this research" sentence to use the [[Page Title]] form that matches the target blog post's note title (locate the current URL in the "More details on this research can be found in this [blog post](...)" line and swap it to the corresponding [[SPIRAL; Letting LLMs Teach Themselves Through Self-Play]] wikilink).
16-16: Use more descriptive link text.Line 16 uses "here" as link text, which is not descriptive for accessibility and SEO. Consider replacing with text that describes the destination.
♻️ Proposed improvement
-Both [Yuya](https://x.com/3un01a) and [Vince](https://x.com/vintrotweets/) will be in Rio - sign up [here](https://plasticlabs.typeform.com/to/xGkkaAEY) to get in touch! +Both [Yuya](https://x.com/3un01a) and [Vince](https://x.com/vintrotweets/) will be in Rio — [sign up to get in touch](https://plasticlabs.typeform.com/to/xGkkaAEY)!🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/research/Plastic` Labs at ICLR 2026.md at line 16, Replace the non-descriptive link text "here" in the sentence "Both [Yuya] and [Vince] will be in Rio - sign up [here](...)" with a descriptive phrase that conveys the destination, e.g., "sign up to meet Yuya and Vince in Rio" or "register for the Plastic Labs Rio meetup"; update the link text in the markdown so the anchor clearly describes the target for accessibility and SEO while leaving the URL unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Around line 87-88: Replace the Obsidian wikilink image syntax
(![[selfplay.png]]) with a standard Markdown image reference pointing to the
project's assets directory and include a descriptive alt text; specifically,
swap the wikilink for a Markdown image that references ../assets/selfplay.png
(alt text like "Self-play training visualization" or similar) in the "Plastic
Labs at ICLR 2026.md" content so the image renders correctly in Markdown.
- Around line 43-44: The image reference on the content line uses the wrong
filename and path; update the Markdown image tag that currently points to
"icrl2026_sampler_results.png" so it uses the correct filename
"iclr2026_sampler_results.png" and the relative assets path
"../assets/iclr2026_sampler_results.png" (replace the existing `` occurrence accordingly).
---
Duplicate comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Around line 30-32: Update the image reference string used in the markdown
figure to follow the content-section asset convention: replace
"iclr2026_sampler_diagram.png" with "../assets/iclr2026_sampler_diagram.png" in
the markdown image tag (the line containing the Figure 1 image reference) so the
file uses the required relative path; also scan the same paragraph for any other
direct asset filenames and apply the same "../assets/..." convention to ensure
consistency.
- Around line 75-76: Update the image reference to use the project's
asset-relative path convention: replace the direct filename
iclr2026_logitscope_ui.png in the content block (the Figure 3 markdown line)
with ../assets/iclr2026_logitscope_ui.png so the asset is referenced as
../assets/iclr2026_logitscope_ui.png for correct resolution from the content
section.
---
Nitpick comments:
In `@content/research/Plastic` Labs at ICLR 2026.md:
- Line 102: Replace the hardcoded external URL in the markdown link
("https://blog.plasticlabs.ai/research/SPIRAL;-Letting-LLMs-Teach-Themselves-Through-Self-Play")
with an Obsidian-style wikilink to the internal blog page; update the link text
in the "More details on this research" sentence to use the [[Page Title]] form
that matches the target blog post's note title (locate the current URL in the
"More details on this research can be found in this [blog post](...)" line and
swap it to the corresponding [[SPIRAL; Letting LLMs Teach Themselves Through
Self-Play]] wikilink).
- Line 16: Replace the non-descriptive link text "here" in the sentence "Both
[Yuya] and [Vince] will be in Rio - sign up [here](...)" with a descriptive
phrase that conveys the destination, e.g., "sign up to meet Yuya and Vince in
Rio" or "register for the Plastic Labs Rio meetup"; update the link text in the
markdown so the anchor clearly describes the target for accessibility and SEO
while leaving the URL unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: da755793-5204-484b-be15-ef58c6cbeefb
📒 Files selected for processing (1)
content/research/Plastic Labs at ICLR 2026.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit