UI: Files island — 'File operation failed (status 404)' when creating folder #56

New issue

Open

opened 2026-04-15 13:34:51 +00:00 by zaelgohary · 2 comments

zaelgohary commented

2026-04-15 13:34:51 +00:00

Member

Description

When attempting to create a new folder in the Files island, the operation fails with an error banner:

File operation failed (status 404)

The folder name input appears correctly and accepts text, but submitting the folder name triggers a 404 from the backend.

Steps to Reproduce

Open Files island from dock
Click "New folder" toolbar button
Enter a folder name (e.g. "test_folder")
Press Enter or click Create
Observe error: "File operation failed (status 404)"

Expected

Folder should be created in the current directory.

Root Cause

The Files island's backend API endpoint for folder creation is returning 404 — the OSIS file service may not be running or the route is misconfigured.

Severity

High — core file management functionality is broken

## Description When attempting to create a new folder in the Files island, the operation fails with an error banner: > File operation failed (status 404) The folder name input appears correctly and accepts text, but submitting the folder name triggers a 404 from the backend. ## Steps to Reproduce 1. Open Files island from dock 2. Click "New folder" toolbar button 3. Enter a folder name (e.g. "test_folder") 4. Press Enter or click Create 5. Observe error: "File operation failed (status 404)" ## Expected Folder should be created in the current directory. ## Root Cause The Files island's backend API endpoint for folder creation is returning 404 — the OSIS file service may not be running or the route is misconfigured. ## Severity High — core file management functionality is broken

deep_files_ctx_01_menu_open.png

65 KiB

zaelgohary commented

2026-04-15 13:34:52 +00:00

Author

Member

Screenshots

deep_files_ctx_01_menu_open.png

## Screenshots ### deep_files_ctx_01_menu_open.png ![deep_files_ctx_01_menu_open.png](https://forge.ourworld.tf/attachments/fe651b9e-bdd6-49a9-a5be-40fec33fb0d1)

zaelgohary commented

2026-04-15 15:26:00 +00:00

Author

Member

Root Cause Found

Network capture shows the exact failing request:

POST http://127.0.0.1:9988/hero_foundry/rpc/api/files/geomind/network_test_folder?action=mkdir → 404

File operations go through hero_foundry RPC. The endpoint /hero_foundry/rpc/api/files/ returns 404 because the hero_foundry service is not running.

This affects all file operations: create folder, create file, rename, delete, copy, move.

## Root Cause Found Network capture shows the exact failing request: ``` POST http://127.0.0.1:9988/hero_foundry/rpc/api/files/geomind/network_test_folder?action=mkdir → 404 ``` File operations go through `hero_foundry` RPC. The endpoint `/hero_foundry/rpc/api/files/` returns 404 because the **hero_foundry service is not running**. This affects all file operations: create folder, create file, rename, delete, copy, move.