Docs: Update GEMINI.md with MCP tool registration issue.

This commit is contained in:
Scott Idem
2026-01-08 12:55:55 -05:00
parent 802c75bad9
commit 9ee2ed444b

View File

@@ -37,16 +37,20 @@ I am the **primary orchestrator and main helper** for the development of the **U
## Current To-Do List
### 1. High Priority & Urgent (UE-AE-01 Orchestration)
- [ ] **Log Dashboard**: Design a way to easily "watch" the `live_logs.txt` without high tool overhead.
- [ ] **Log Dashboard**: Find a way to "stream" `live_logs.txt` back to you/agents efficiently.
- *Note:* Initial `view_live_logs` tool implemented, but MCP tool registration is currently failing.
- [ ] **Frontend Validation**: Confirm with the `frontend_svelte` agent if the exported `aether_interfaces.ts` meet their requirements.
### 2. Infrastructure & Technical Debt
- [ ] **Agent Bridge Restoration**: Repair and uncomment the `agent_bridge` router.
- *Plan:* Wrap `psutil` imports in try/except; metrics will be "Degraded" until container build updated with C-build tools.
- [ ] **Docker Registry Sync**: Verify if all running containers match the expected images in `docker-compose.yml`.
- [ ] **Agent Bridge Restoration**: Repair the metrics router (`agent_bridge.py`). I'll implement a "safe" version that doesn't crash if `psutil` is missing.
- [ ] **Docker Registry Sync**: Audit `docker-compose.yml` against the actual running containers to ensure env vars and volumes are consistent.
### 3. Deferred / Paused
- [ ] **Psutil Container Update**: Postponed until higher priority (requires image rebuild with build-essential).
- [ ] **Psutil Container Update**: Rebuilding the API image with C-build tools (GCC) to support native system monitoring.
### 4. MCP Tooling Debug (NEW)
- [ ] **MCP Tool Registration Issues**: Investigate why newly added tools are not being registered/discovered by the MCP server, even after restart. This affected `ae_obj_info` and `view_live_logs`.
### Workflow & Collaboration
- **Storage**: Critical assets at `/home/scott/OSIT/hosted_files/` (Synced via Syncthing).