# CoReMem: Cost-Internalizing Memory for Successive Coding Tasks with Prospective Valuation

Source: [arXiv](https://arxiv.org/abs/2611.17316v1)  
Feed7 permalink: https://feed7.dev/p/2611-17316v1-0cco6aj  
Published: 2026-11-12T18:58:22.000Z  
Trust: Needs Review (needs_review)

## Why Included

CoReMem tests repository memory by measuring whether stored task traces help on the next task. On ChainSWE, it improved a 27B actor’s resolve rate while reducing steps and token use.

## Source Summary

CoReMem selects compact repository memory by comparing task runs with and without trajectory segments, then adapts the agent based on measured memory value. Its memory centers on **repository locations** and **executable checks**.

## Practical Implication

For builders running agents across successive tasks, this suggests keeping memory tied to actionable anchors and evaluating whether those anchors reduce work on later tasks.

## Agent-Ready Context

CoReMem selects compact repository memory by comparing task runs with and without trajectory segments, then adapts the agent based on measured memory value. Its memory centers on **repository locations** and **executable checks**.

For builders running agents across successive tasks, this suggests keeping memory tied to actionable anchors and evaluating whether those anchors reduce work on later tasks.

On ChainSWE, the **27B actor** improved resolve rate from **21.0% to 25.7%**, with 17% fewer steps and 11% fewer cache-aware tokens. The result is from one benchmark; the abstract does not establish how well it transfers to other repositories or workflows.

## Connected Context

Feed7 judgment across 1089 accumulated Signals:

CoReMem treats repository memory as a measured investment: it tests trajectory segments against later task outcomes and retains actionable locations and checks. Its ChainSWE result suggests this can help across successive coding tasks, but transfer beyond that benchmark remains open.

- [Procedural Graphs: Self-Evolving Execution Structures for LLM Agents](https://feed7.dev/p/2609-09153v1-0ee5zbi) — Both make agent memory actionable for later work. Procedural Graphs refine executable workflows from outcomes, while CoReMem evaluates whether specific trajectory segments help subsequent tasks, adding prospective value measurement to the workflow-memory idea.
- [Effective harnesses for long-running agents](https://feed7.dev/p/effective-harnesses-for-long-running-agents-0xzfs05) — The harness pattern stores progress across sessions and verifies features end to end; CoReMem adds evidence that repository locations and executable checks can be selected by their measured effect on later tasks.

## Context Map

- Layer: agent
- Domains: coding
- Topics: agent-memory, harness-engineering

## Uncertainty

- On ChainSWE, the **27B actor** improved resolve rate from **21.0% to 25.7%**, with 17% fewer steps and 11% fewer cache-aware tokens. The result is from one benchmark; the abstract does not establish how well it transfers to other repositories or workflows.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
