Skip to content

docs: mention Zoo Code as the Roo Code community successor - #85

Open
taltas wants to merge 3 commits into
cyberagiinc:feature-mainfrom
taltas:add-zoo-code-readme
Open

docs: mention Zoo Code as the Roo Code community successor#85
taltas wants to merge 3 commits into
cyberagiinc:feature-mainfrom
taltas:add-zoo-code-readme

Conversation

@taltas

@taltas taltas commented Jul 19, 2026

Copy link
Copy Markdown

Roo Code (RooCodeInc/Roo-Code) was archived / shut down on May 15, 2026 and is now
read-only. Its own repo notes the community successor here:
https://github.com/RooCodeInc/Roo-Code#disclaimer

Zoo Code is the community-maintained fork that continues where Roo Code left off:

This PR adds a Zoo Code reference alongside the existing Roo Code mention in the README so
readers looking for a maintained alternative can find it.

Shubham-Khichi and others added 3 commits April 10, 2025 16:00
…yberagiinc#48)

Patch Fixes: 

- Fixed MCP Docker Build Failure: Resolved the build error for the mcp
service by removing the invalid readme reference in
fast-markdown-mcp/pyproject.toml.
- Refactored File Handling (Removed In-Memory Storage):
- Investigated the complex in-memory file handling mechanism and its
inconsistencies.
- Removed the in-memory storage logic from backend/app/crawler.py.
- Removed the associated API endpoints (/api/memory-files,
/api/memory-files/{file_id}) from backend/app/main.py.
- Added a new backend API endpoint (/api/storage/file-content) to read
files directly from the storage/markdown directory.
- Deleted the old frontend API proxy route
(app/api/memory-file/route.ts).
- Created a new frontend API proxy route
(app/api/storage/file-content/route.ts).
- Updated frontend components (StoredFiles.tsx, DiscoveredFiles.tsx) to
use the new API route for downloading file content.
- Documentation: Created markdown plans for the MCP build fix and the
in-memory feature removal.
- This simplifies the architecture by relying solely on disk-based
consolidated files in storage/markdown. Please remember to test the file
download functionality after restarting the services.

feat: Enhance crawl workflow, UI, and fix backend issues
This commit addresses several issues and implements enhancements across
the crawling workflow:

Fixes:
- Resolved 400 Bad Request error caused by incorrect query parameter
(`file_path`) in the file content API route.
- Fixed backend `NameError` (`set_task_context`) in crawler.py that
prevented result file saving.
- Corrected 500 Internal Server Error caused by Docker networking issue
(localhost vs. service name) in the file content API route proxy.
- Ensured 'Data Extracted' statistic is correctly saved in the backend
status and displayed in the UI.

UI Enhancements:
- Made "Consolidated Files" section persistent, rendering as soon as a
job ID is available.
- Relocated "Crawl Selected" button inline with status details.
- Updated "Crawl Selected" button to show dynamic count and disable
appropriately.
- Renamed "Job Status" section title to "Discovered Pages".
- Renamed "Processing Summary" section title to "Statistics".
- Removed the unused "Extracted Content" display section.

Backend Enhancements:
- Implemented file appending logic in crawler.py for consolidated `.md`
and `.json` files. Subsequent crawls for the same job now append data
and update timestamps instead of overwriting.


feat(frontend): Update Consolidated Files component for polling and
downloads

- Implements polling every 10 seconds in ConsolidatedFiles.tsx to
automatically refresh the list of files from the /api/storage endpoint,
ensuring newly added files appear in the UI.
- Modifies the MD and JSON icon links to point to the
/api/storage/download endpoint and adds the 'download' attribute,
triggering file downloads instead of opening content in the browser.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants