{"id":8616,"date":"2026-09-13T13:01:33","date_gmt":"2026-09-13T13:01:33","guid":{"rendered":"https:\/\/justfineinfotech.com\/coding-agents-dont-need-longer-history-they-need-intent-continuity-towards-data-science\/"},"modified":"2026-09-13T13:01:37","modified_gmt":"2026-09-13T13:01:37","slug":"coding-agents-dont-need-longer-history-they-need-intent-continuity-towards-data-science","status":"publish","type":"post","link":"https:\/\/justfineinfotech.com\/fr\/coding-agents-dont-need-longer-history-they-need-intent-continuity-towards-data-science\/","title":{"rendered":"Coding Agents Don’t Need Longer History \u2014 They Need Intent Continuity | Towards Data Science"},"content":{"rendered":"
text<\/p>\n
Retrieval asks:\"What historical information might be relevant?\"Verification asks:\"Is that information still valid?\"Intent continuity asks:\"What historical intent should influence this task, right now?\"<\/code><\/pre>\n\nThe intent-continuity pipeline, horizontal flow. Nine steps carry a coding agent’s historical requirements from raw interaction history, through verification and supersession checks, to a graded implementation. No embeddings, no vector database, no LLM call in the pipeline.<\/figcaption>This diagram maps how an AI coding agent recovers and verifies project requirements from earlier conversations instead of relying on a longer context window or plain vector search. Interaction history moves left to right through rule-based intent extraction, then drops down and continues right to left through candidate retrieval and verification, where superseded or out-of-scope decisions get dropped before anything reaches the agent. The pipeline ends with a deterministic agent and a requirement checker, so every recovered requirement is graded the same way it was verified. The whole system runs in pure Python, with no embedding model or vector database anywhere in the chain. \n<\/figure>\n
python<\/p>\n
# extractor.py (abridged)TRIGGER_PHRASES = [\"must\", \"never\", \"required\", \"require\", \"prefer\", \"should\",\"always\", \"migrating\", \"let's use\", \"default\", \"for now\",]def _looks_like_requirement(text: str) -> bool:lower = text.lower()return any(phrase in lower for phrase in TRIGGER_PHRASES)<\/code><\/pre>\n
# compiler.py \u2014 resolution rule, applied identically for every conditiondef compile_context(context_records):provenance = {}for record in sorted(context_records, key=lambda r: r.index):provenance[record.effect_key] = record # later overwrites earlierfields = {key: r.effect_value for key, r in provenance.items()}token_estimate = sum(len(r.text.split()) for r in context_records)return fields, provenance, token_estimate<\/code><\/pre>\n\nWhy “found something related” isn’t the same as “found what’s current.” Both mechanisms retrieve the same two historical records; only one determines which is still valid before handing it to the agent.<\/figcaption>This diagram walks through a real supersession case from the intent-continuity experiment: an early decision to use JWT-based authentication, later replaced by a decision to migrate to OAuth2. Naive lexical retrieval, the kind of behavior you’d get from plain keyword or vector similarity search, finds both records and lets the newer one win purely because it was mentioned more recently, a coincidence of ordering rather than an actual validity check. Intent-aware retrieval finds the same two records but runs an explicit verification step that determines the older record is superseded before either one reaches the coding agent. Both approaches land on the correct auth method in this particular case, which is exactly the point: one got there by luck, and the other by design, and that difference is invisible until you test a case where the ordering doesn’t happen to save you. \n<\/figure>\n\nTasks passed out of 8, by condition. Going from no history, to naive lexical retrieval, to intent-aware retrieval doubles task correctness and then doubles it again.<\/figcaption>This bar chart shows the final task-completion results from the intent-continuity experiment across the same 8 coding tasks. A coding agent with no access to history passed 0 of 8 tasks, breaking a requirement it was never told still applied. Naive lexical retrieval, the kind of result you’d expect from basic keyword or vector-similarity search with no validity checking, passed 4 of 8. Intent-aware retrieval, which adds an explicit verification step to drop superseded or out-of-scope requirements before they reach the agent, passed all 8. The gap between naive retrieval and intent-aware retrieval is the actual finding of this experiment: retrieving related history isn’t the same as retrieving requirements the agent can currently trust. \n<\/figure>\n
![\"Horizontal](\"https:\/\/justfineinfotech.com\/wp-content\/uploads\/2026\/09\/1788926622698_u9zqf8.png\")
![\"Diagram](\"https:\/\/justfineinfotech.com\/wp-content\/uploads\/2026\/09\/1788926622708_dkqche.png\")
![\"Bar](\"https:\/\/justfineinfotech.com\/wp-content\/uploads\/2026\/09\/1788944398649_uxro4j.png\")