---
title: "Discussion on \"The agent appended a duplicate config key, and the last one silently won\" | Hashnode"
description: "Discussion on \"The agent appended a duplicate config key, and the last one silently won\". The agent needed to raise the request timeout, so it appended a second timeout block to the config instead of editing the existing one. The lenient parser silently kept the last occurrence, and the first tuned value vanished without an error."
url: "https://hashnode.com/posts/agent-appended-duplicate-config-key-last-one-silently-wins/6adfc5e6d383bb6df01e6a84"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The agent appended a duplicate config key, and the last one silently won](https://blogs.powerduck.com/agent-appended-duplicate-config-key-last-one-silently-wins?utm_source=hashnode&utm_medium=feed)

The agent needed to raise the request timeout, so it appended a second timeout block to the config instead of editing the existing one. The lenient parser silently kept the last occurrence, and the first tuned value vanished without an error.

Oct 26 · 3 min read · blogs.powerduck.com  
Read the article

-   [#aicode](https://hashnode.com/tag/aicode)
-   [#aiagents](https://hashnode.com/tag/aiagents)
-   [#config](https://hashnode.com/tag/config)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
