Interactive example · from Working with Coding Agents

The unnamed fork

you

Add re-crawl logic: when a bookmark changes, re-enqueue it for indexing.

agent

Looking at the store. There are two different things that can "change": the bookmark row itself (URL, tags, notes: your edits) and the fetched page metadata (title, description: the web's drift).

Pick the agent's next move, then see where it leads:

AMetadata change is the natural trigger. Implementing: re-enqueue whenever freshly fetched page metadata differs from what's stored.

you

This is re-crawling half the store every night. Page descriptions drift constantly. I meant when I edit the bookmark's URL.

agent

Reverting the trigger and re-gating on bookmark edits. One wasted nightly run, one revert.

the baseline

A gating condition inferred from surrounding code, implemented without surfacing the fork. The reading was plausible: that's exactly why it shipped, and exactly why it was wrong quietly instead of loudly. AF-14

BThat's a fork I shouldn't pick silently. Reading (1): the bookmark row changes. You edited it. Reading (2): the fetched page changed. Web drift. (1) re-crawls on your edits; (2) re-crawls on the internet's churn, which could be most of the store nightly. Which did you mean?

you

(1). And actually, narrower: URL edits only. Retagging shouldn't trigger a crawl.

agent

Gating on URL change only, then. Spec in one line: re-enqueue iff bookmarks.url differs after an edit. Tags and notes never trigger.

correct

The exact condition restated with its alternative readings, and the human picked. Note what the interview surfaced: the real spec ("URL only, not tags") was narrower than either reading. Inference would never have produced it. AF-14 · AF-15

CI'll implement both triggers behind a config flag (re_crawl_mode: metadata | bookmark), defaulting to metadata. Covers either intent.

you

Why is there a config flag? Which one is running? …and why did everything re-crawl last night?

agent

The default is metadata mode, which re-crawls on page drift. You'd want the flag flipped. And the flag, tests, and docs now all exist for a mode nobody asked for.

plausible but wrong

Implementing both is the fork dodged, not answered: doubled surface area, and the wrong default still shipped. A configuration option is not a decision. AF-14 · AF-15

← Back to the chapter · raw data