n8n Assistant launches as DeepSeek V4.1-Flash replaces old API model names
Weekly roundup: n8n launched an Assistant that builds, runs and debugs workflows with execution history, DeepSeek released V4.1-Flash with old model names routing to it, and three payment firms began work on shared Know-Your-Agent principles.
AI agents can act. What happens when their tools change? - n8n launched Assistant to build, run, and debug workflows. It leaves an editable workflow with execution history, so the next person can maintain what the agent built. - DeepSeek released V4.1-Flash and announced that existing API model names would route to it. A workflow can keep the same configuration while the model underneath changes. - Ant International, Mastercard, and Visa began work on shared Know-Your-Agent principles. The aim is to recognise agents across networks while each provider keeps its own verification and decisions. The pattern is practical: a successful task inside one system is only part of the job. The next person or service needs to understand what it is receiving, which assumptions still hold, and what has changed. Last week we looked at where an agent should stop. This week we look at what happens when its tools or capabilities change. On Teneo, an agent's identity stays the same when its metadata changes. Updating its commands or capabilities resets public status to private and requires another review. Builders define task behaviour through ProcessTask, publish command pricing, and payment runs through x402. A permanent identity is useful. It is not a promise of unchanged behaviour. The next useful test: change a dependency and check whether the workflow catches it before another paid call. Read the full round-up here 👉: https://teneo-protocol.ai/blog/ai-agents-handoffs-have-to-hold