vendor lock in via context

2 articles · 12 co-occurring · 0 contradictions · 0 briefs

R00mi explicitly identifies proprietary Routines/Projects as lock-in vectors, contrasted with portable MCP+CLAUDE.md architecture

Related concepts

tool integration patterns 2 multi agent orchestration 2 context window management 2 tacit to explicit knowledge 1 model selection strategy 1 mcp as portable context abstraction 1 human ai collaboration 1 harness interchangeability 1 context preservation across sessions 1 context as strategic asset 1 ai agent architecture 1 agent design patterns 1

Evidence chain (2 articles, showing 2)

What Claude Code's Source Revealed About AI Engineering Culture | Hacker News example_of

R00mi explicitly identifies proprietary Routines/Projects as lock-in vectors, contrasted with portable MCP+CLAUDE.md architecture

@dexhorthy: "think before you AI" - "do not outsource the thinking" - this is a great, ti... supports

Author warns: 'avoid tools that want to hoard your context to create a moat.' This identifies a critical anti-pattern where vendors use context opacity as a retention mechanism.

query this concept

$ db.articles("vendor-lock-in-via-context")

$ db.cooccurrence("vendor-lock-in-via-context")

$ db.contradictions("vendor-lock-in-via-context")