You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Conversations now use one Pi-native AgentSession path. Opening or switching a conversation restores local history while activating its AgentSession, so it is ready to continue.
Conversations can be created, renamed, archived, restored, and soft-deleted. Archived conversations moved from the chat dialog to Settings → EchoInk → Review, while the original Pi Session JSONL remains intact.
The conversation header, message actions, and composer toolbar were rebuilt. The send button is smaller, and low-value Agent status and knowledge-health widgets were removed.
Visible, correctable long-term memory
Current Memory is grouped into Facts, Views, Decisions, Active, and Episodes. Each record shows its title, content, and recall context without exposing internal paths or revisions.
The correction dialog keeps the original memory, correction input, and cyan corrected preview visible together. Preview generation can be stopped and never writes the original record.
Only Save creates a new version. Editing the input immediately invalidates an old preview; closing, stopping, failure, late results, and revision conflicts cannot overwrite current Memory.
Direct knowledge maintenance and review
/maintain without arguments runs globally. Selecting one Raw note with the composer's + targets that note, while trailing text fuzzy-searches related Raw notes.
Already-refined content with no changes settles without another write. Candidates are bound to target revisions, preventing a generated result from overwriting newer content.
Report generation and destination settings now share one Review page. Choose Agent or knowledge-base reports, the date range, any vault folder, and whether to open the generated HTML. The recent-report list has been removed.
Providers and upgrade notes
Provider setup now stores API keys directly and no longer requires a separate Credential step. Existing configurations that contain only a retired Credential reference require the API key to be entered once.
EchoInk 2.0 does not read or migrate retired Codex, OpenCode, or Hermes conversations, or retired Cognitive, Reflection, and Memory data. It does not proactively delete those old files.
Obsidian 1.11.4 or later is required, and EchoInk remains desktop-only. Keep a vault snapshot before upgrading, following your normal backup practice.