Hitting the file limits while creating a detailed technical documentation

[rajathkannabiran]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

macOS 26.2

Kiro Version

0.8.206

Bug Description

While creating a technical documentation draft, i was hitting a cap for file size.
While retry worked by slowly appending contents chunk by chunk, it failed in the first try and also took massive amount of time about 20minutes.

1. Either the text arg was not provided or text content provided exceeded the write file limit of 50 lines. The agent has seen this error and will try a different approach to write the file if needed.
2. Due to the length of the document, let me continue appending the remaining sections

File info: 4800 lines of a text file
File size: 135 KB

Steps to Reproduce

1. Take a heavy analysis and documentation task. Example: analyzing and documenting A to Z about a micro-service codebase

Expected Behavior

I expect a writing on file to be more efficient

Conversation ID

No response

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #4879: During long dialogues or editing of large files, the oldStr parameter of the strReplace tool may be truncated, resulting in an inability to match the file content (85% similar)
• #3615: File creation/editing not working (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ Remove the duplicate label if this is NOT a duplicate
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both issues deal with file size limitations and handling of large files. The new issue reports hitting file limits when creating documentation (50 line limit, 4800 lines total), while #4879 reports truncation issues with large files in the strReplace tool. Both involve problems processing large content that exceeds system limits.

[github-actions]

This issue has been automatically closed as it appears to be a duplicate of an existing issue.

If you believe this is incorrect, please comment on this issue and a maintainer will review it.

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.