# Before you buy an AI agent, make it pass an exit test

DevFeed: [Before you buy an AI agent, make it pass an exit test](<https://devfeed.tech/articles/before-you-buy-an-ai-agent-make-it-pass-an-exit-test-114880.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4243401/before-you-buy-an-ai-agent-make-it-pass-an-exit-test.html>)

Author: Suneet Malhotra

Published: 2026-11-03T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [long-running](<https://devfeed.tech/topics/long-running.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-development-tools-software-development](<https://devfeed.tech/tags/artificial-intelligence-development-tools-software-development.md>), [cli](<https://devfeed.tech/tags/cli.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [exit](<https://devfeed.tech/tags/exit.md>), [export](<https://devfeed.tech/tags/export.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [memory](<https://devfeed.tech/tags/memory.md>), [migration](<https://devfeed.tech/tags/migration.md>), [model](<https://devfeed.tech/tags/model.md>), [models](<https://devfeed.tech/tags/models.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [standards](<https://devfeed.tech/tags/standards.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [test](<https://devfeed.tech/tags/test.md>)

## AI overview

The article argues that switching AI agents can leave behind the state of ongoing work even when models, protocols, and chats are portable. It proposes a one-day exit test using a realistic maintenance task: stop one agent halfway, export its requirements, decisions, completed work, and remaining steps, then give only that export to a fresh agent--ideally from another vendor. Check whether it repeats finished changes, revives an assumption a human explicitly retired, how many minutes a person spends restoring context, and which instructions, skills, hooks, or credentials break. Run the test both within one product and across vendors; record the task, export size, failures, and human time, ask vendors to demonstrate their actual exit export, and repeat at renewal. The test measures switching cost rather than proving a free switch: some model-specific skills may not transfer even with compatible formats.

## Source excerpt

I recently moved my own setup from one coding agent to another. It took about 10 minutes and I thought it went well. The first agent had a lot to carry. Today it has a global instruction file, 114 skill folders (most installed, a few written by me), 189 small memory notes spread across 24 projects and 73 scripts that shell out to its command-line tool. To give a second agent the same footing, I copied the instruction file to the name the other tool reads, AGENTS.md, and ran a find-and-replace on the product name. I didn't read the result properly until this month. It tells the new agent to make every model call with Codex -p. In that CLI, -p is short for -profile. Followed literally, my instruction loads a configuration profile named after whatever prompt it was handed. The same file still warns the new agent, in bold, never to use the old vendor's API key, a key it had no reason to go near. Nothing errored. The file sat in my home directory for almost three months looking like a finished migration. That is the exit problem in miniature. I could switch models in an afternoon. The work didn't come with it, and nothing told me. Portability claims stop at the model Vendors have learned to answer the lock-in question. Ask about switching and you hear about model choice, standard protocols and conversation export. InfoWorld has already made the case that the new AI lock-in lives in the layers around the model rather than in the model. The standards side is moving too. MCP and AGENTS.md now sit under the Linux Foundation's Agentic AI Foundation, which is good news for the plumbing. None of that tells you whether a half-finished job survives a change of agent. An agent that has worked in your codebase for six months has picked up things that are neither the model nor the transcript: decisions it was told to respect, approaches it tried and dropped, changes it made, changes it only planned and the permissions and hooks wired around it. Exporting a conversation gives you a r