0 Fork 0

Files

T

Evandro Fonseca Junior 5f86c69b03 fix: restore standard chat message flow - remove broken ForgeAgent integration

- Removed complex ForgeAgent state management from ChatView and MessageBubble
- Messages now display as simple text with markdown rendering
- Removed useMemoryExtractor hook and memory system prompt logic
- Simplified message persistence (no forgeagent_state column)
- Fixed agentic mode to show AI response as text instead of fake plan

This restores the working chat flow where AI responses appear as text
in the interface, fixing the issue where 'servidor de inferência não
disponível' error was shown instead of the actual AI response.

2026-04-02 16:05:31 -03:00

6.1 KiB

Raw Blame History

gsd_state_version, milestone, milestone_name, status, stopped_at, last_updated, last_activity, progress

gsd_state_version

milestone

milestone_name

status

stopped_at

last_updated

last_activity

progress

1.0

v1.0

milestone

active

Completed Phase 6 - Chat UI Redesign

2026-04-02T12:20:00.000Z

2026-04-02

total_phases	completed_phases	total_plans	completed_plans	percent
6	4	16	16	75

Project State

Project Reference

See: .planning/PROJECT.md (updated 2026-03-28)

Core value: A user can configure and operate the runtime from one trustworthy workspace without the UI fighting their in-progress edits. Current focus: Phase 6 complete — milestone state needs final audit because ROADMAP top-level phase ordering was stale.

Current Position

Phase: 6 of 6 (Chat UI Redesign) Plan: 4 of 4 completed for current phase Status: Phase complete — verified Last activity: 2026-04-02 - Completed Manus-style agentic transcript blocks and Tauri event bridge scaffold

Progress: [███████░░░] 75%

Performance Metrics

Velocity:

Total plans completed: 12
Average duration: 13min
Total execution time: ~2.6 hours

By Phase:

Phase	Plans	Total	Avg/Plan
01	3	46min	15min
02	3	33min	11min
03	3	39min	13min
04	3	45min	15min

Recent Trend:

Last 5 plans: 04-03 (15min), 04-02 (15min), 04-01 (15min), 03-03 (13min), 03-02 (13min)
Trend: Stable

Accumulated Context

Decisions

Decisions are logged in PROJECT.md Key Decisions table. Recent decisions affecting current work:

Phase 1 starts with state ownership fixes before UI consolidation to eliminate poll-driven draft overwrites first.
This milestone stays brownfield and must preserve working lifecycle, model selection, and chat flows while improving runtime workspace trust.
[Phase 01]: Kept legacy snapshot and saveConfig outputs while adding explicit draft APIs so existing runtime drawer consumers keep compiling during the Phase 1 transition.
[Phase 01]: When a runtime draft is dirty, polling updates only operational live fields and leaves baseline plus draft config untouched.
[Phase 02-lifecycle-command-safety]: Expose active and last lifecycle command data on RuntimeSnapshot so frontend polling can render trustworthy lifecycle feedback without inferring from status alone.
[Phase 02-lifecycle-command-safety]: Centralize duplicate start/stop blocking in runtime state helpers so save, start, and stop flows share the same command-result contract.
[Phase 02-lifecycle-command-safety]: Keep restart-required save enforcement limited to connection_mode, model_path, addr, gpu_layers, and ctx_size to stay aligned with the existing backend runtime boundary.
[Phase 02-lifecycle-command-safety]: Mirror backend lifecycle metadata directly into the frontend RuntimeSnapshot so polling and command responses share one contract.
[Phase 02-lifecycle-command-safety]: Derive applyImpact from saved baseline versus draft config using the backend restart-required field list instead of UI-only heuristics.
[Phase 02-lifecycle-command-safety]: Expose activeLifecycleCommand, lastLifecycleResult, and lifecycleBusy from the manager so status-card and drawer copy can consume explicit state in plan 02-03.
[Phase 02-lifecycle-command-safety]: Use explicit lifecycle result banners instead of overloading last_error so completed and blocked actions remain visible after polling refreshes.
[Phase 02-lifecycle-command-safety]: Render apply guidance in the drawer before the CTA row so users see whether a draft applies immediately, needs restart, or must be saved before apply.
[Phase 02-lifecycle-command-safety]: Keep status-card and drawer props backward-compatible with optional lifecycle fields while Sidebar forwards the new manager contract.
[Phase 03-01]: Reuse existing restart-impact field list and lifecycle labels instead of creating parallel heuristics
[Phase 03-01]: Derive diagnostics from backend-owned snapshot fields (status, ready, process_running, resolved_url, config.*, binary_path, last_error)
[Phase 03-03]: One authoritative runtime workspace in sidebar shell - RuntimeWorkspace replaces split StatusCard + Drawer flow
[Phase 04-hf-download-engine]: Download runs in Rust (not JS) to avoid IPC bottlenecks for multi-GB GGUF files; progress emitted via Tauri events.
[Phase 04-hf-download-engine]: Direct resolve URL https://huggingface.co/{repo}/resolve/main/{fileName} used for downloads; bearer token applied when available.
[Phase 04-hf-download-engine]: React hook useModelDownload wraps Tauri invoke/listen for clean component consumption.
[Phase 04-hf-download-engine]: .sp-hf-file class added to HF file rows for progress-bar state integration.

Pending Todos

None yet.

Blockers/Concerns

ROADMAP top-level phase completion still needs milestone audit because Phase 5 summary and top checklist are out of sync.

Quick Tasks Completed

#	Description	Date	Commit	Directory
1	Investigar e corrigir bug de internal error na segunda mensagem do chat	2026-03-30	`abb9db0`	1-investigar-e-corrigir-bug-de-internal-er

Session Continuity

Last session: 2026-03-31T00:25:00.000Z Stopped at: Completed Phase 4 - Hugging Face Download Engine Resume file: None Phase 5: Model Source Validation is already implemented via runtime validation in Phase 2/3. Marking as complete.

6.1 KiB Raw Blame History