Anchorport

Engineering teams accumulate conventions, architecture notes and do-or-do-not rules in tool-specific instruction files. Switching tools can mean manually translating those records and rediscovering context that was never written down. The supplied research confirms a live memory-native coding agent and a live cross-tool context-sync product. It reports that neither reviewed product performs source-format translation into a canonical context and then emits a target-native configuration. That is a bounded feature comparison, not proof of exclusivity.

Anchorport would preserve repository, branch or revision, source file, source format, source span, extracted statement, extraction confidence, canonical candidate, interpretation note, conflict set, secret finding, unsupported directive, target tool, target capability, rendered target statement, lossy-conversion warning, owner decision, write plan, backup reference, applied revision, destination readback, rollback and deletion as distinct records. Nothing should be written merely because a parser or model produced it.

Instruction files can contain credentials, private URLs, customer names, unsafe commands, stale assumptions and prompt-injection text. A repository scan is not permission to export those contents. The product should default to local processing or explicitly bounded transfer, exclude likely secrets, retain line-level provenance and show every semantic conflict. A target file can preserve wording while changing behavior because agent tools interpret scope, precedence and supported features differently. The system must not claim semantic equivalence where it has only syntax conversion.

The pilot should use synthetic repositories and public fixtures with no credentials. The likely buyer is an engineering lead, platform owner or independent developer switching among coding agents, but tool mix, repository count, security requirements, migration frequency, budget and willingness to pay beyond the confirmed adjacent products remain unverified.

An engineering lead, developer-platform owner or independent developer responsible for consistent coding-agent instructions across repositories and tools.