Skip to content

Agnes Code Platform File Write API Permanently Fails (No Persistence) #94

Description

@wonderwander2026

Describe the bug

Before filing, please check common issues:
https://agnescode.agnes-ai.com/docs/troubleshooting

To help us debug faster, attach your diagnostics ZIP package if possible.

A clear and concise description of what the bug is.

Field | Value -- | -- Report Title | Agnes Code write() / edit() API does not persist file modifications (timestamp unchanged) Reporter | wonde (Windows user) Date Reported | 2026-08-02 UTC-4:00 Severity | 🔴 CRITICAL — All file write operations silently fail Affected Interfaces | agnes_write_file / write() API, agnes_edit_file / edit() API, Python open().write() within agent session Affected Platform | Agnes Code Desktop Agent (Windows environment)

Suggested Fix / Investigation Points

  1. Trace the IPC pathway between the Agnes Agent process and the Windows filesystem — identify where the file handle is opened and whether write calls are actually dispatched to the OS.
  2. Validate privilege context — Is the Agent process running under a different security token / sandboxed context that blocks file I/O?
  3. Check for wrapper interception — There may be a custom file-opener wrapper that redirects to memory/temp location without flushing to disk.
  4. Review async/sync coordination — Could writes be queued but never flushed due to event loop deadlocks or orphaned worker threads?
  5. Add telemetry logging — Log actual OS-level file I/O system call results from within the agent layer to catch silently failing syscalls.

Workarounds / Interim Recommendations

Until the underlying I/O bridge is fixed, users must bypass the Agent's write() entirely:

Option A: Native Terminal Delegation

Have the Agent generate content as text output, then have the user copy-paste into their own terminal/powershell to write manually:

# User runs this AFTER Agent outputs content Set-Content -Path "target.txt" -Value "[AGENT_OUTPUT_CONTENT]"

Option B: Temp + Copy Pattern

Agent writes to a known temp location accessible by user (e.g., %TEMP%\agent_output\tempfile.txt), then user copies with robocopy or drag-and-drop.

Option C: Cloud Sync Folder Trick

OneDrive/Google Drive sync folders sometimes bypass certain sandbox restrictions — try writing to a synced folder instead of local workspace.

Option D: Switch Platforms

For tasks requiring reliable file persistence, use a different AI agent platform (as validated earlier: Codex/platform works reliably).


Attachments (to be provided separately)

  • Screenshot of file properties showing unchanged timestamp after write attempts
  • Video demonstration of repro steps (optional)
  • Diagnostic ZIP with logs (if available)

Conclusion

This is a fundamental infrastructure bug: the Agnes Agent cannot save anything to the filesystem. Without resolving this, any development task requiring local output—code generation, skill creation, report writing, dashboard export—is impossible on this platform. The severity level must be elevated to critical/blocker status.

AgnesAI Labs team, please prioritize investigation of the Agent-filesystem I/O bridge layer. We recommend reproducing on a clean Windows VM to rule out user-side configuration differences, then tracing the actual OS syscall chain from the Agent process entry point down to disk.

Thank you for your attention to this matter.


Reporter: wonde
Contact: [Your Email / Preferred Channel]
Date: 2026-08-02


To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.


Screenshots
If applicable, add screenshots to help explain your problem.


Please provide the following information

  • OS & Arch: windows 6.2.9200 x86_64
  • Interface: UI
  • Version: 1.44.0
  • Extensions enabled: agnes_slide, developer, skills, analyze, todo, summon, agnes_web_search, agnes_research, agnes_artifacts, agnes_aigc, tom, Extension Manager, autovisualiser, chatrecall, computercontroller
  • Provider & Model: agnes - agnes-2.5-flash

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions