Fresh-Continue

List all tracked projects with progress, status metrics, current active nodes and ready-next nodes.

Read the complete current project graph, dependencies, decisions, checkpoints and node state before continuing work.

Return a concise "where you left off" card: current step, next step, last meaningful activity, checkpoint and attention items. Use when returning to a project after a gap or when the user asks where they were.

Read broad areas such as work, personal, social and wellbeing. Areas are viewing/classification lenses, not object types.

Read dated project steps, deadlines, reminders and life/context plans in one chronological projection without duplicating the underlying objects.

Find overlapping scheduled project work and explicit life/context plans across Fresh Continue. Use before committing a new time when a cross-project, social or personal conflict is plausible. Deadlines and notification reminders are not treated as occupied time.

Read people explicitly linked to plans/tasks/context and their open work or remembered plans. Use when the user asks what is going on with a person, what they owe/expect, or before changing a person-related plan.

Read items that intentionally left the active flow but were not deleted. Use when recalling abandoned ideas, cancelled meetings/work or deciding whether to revive something.

Change lifecycle without deleting history. Use cancelled for explicit "not doing / cancelled / will not happen" intent, archived for intentionally shelved/reference-only items, and active to revive/restore. Cancelled is not Done.

Create a new tracked project. Use project_plan_set afterwards to build its dependency graph.

Replace/reconcile the project roadmap graph. Existing completed nodes with matching IDs remain completed. Dependencies drive Ready/Locked state automatically.

Simulate changing a node schedule/deadline and show downstream dependencies, equivalent shifted dates, calendar collisions and pending plan reviews. Use before meaningful postponements or replanning; this tool never writes changes.

Update a roadmap node after real progress. Dependency locks are enforced by the core service.

Attach durable project context that is not necessarily code: notes, deliverables, references, URLs, metrics/KPIs, design decisions, user feedback, published assets, content ideas, research findings or other evidence. Use this for non-software projects as well as software projects.

Read project notes, deliverables, references, metrics and other evidence independent of Git or a local workspace.

Record a meaningful architectural/product decision and its reason so later AI sessions do not rediscover or contradict it.

Create a checkpoint after a meaningful work session with summary, blockers, decisions and concrete next actions.

Read overdue, today, upcoming, recurring check-ins and reminders across all projects. Use for “bugün ne var?”, agenda, daily planning, deadline review and life-goal follow-up.

Find plan confirmations, stale open work, deadline risks, unscheduled active steps, waiting items, conversational flags, loose life commitments and people/entity context across Fresh Continue. Use to answer “what am I forgetting?”, during periodic reviews, or before replanning.

Prepare a calm weekly review from recent activity plus the memory radar: changed plans, stale work, unscheduled items, deadline risks and loose commitments. This is a review aid; it does not alter plans automatically.

Create a Windows-notification reminder for a project or roadmap node. Supports one-time, daily, weekly and monthly repetition.

Record a daily/weekly progress check-in for recurring goals, habits, agenda items or long-running roadmap nodes without permanently marking the node Done.

Capture a concrete fact/change/commitment/cancellation/constraint from conversation when it can affect future plans. Link it to existing project steps and describe the impact. Conflicts/changes create a confirmation review instead of silently altering the plan.

Look up recent active future-affecting facts, plans and commitments, optionally by person/entity, before deciding whether a new conversation detail conflicts with something already remembered.

Read unresolved “is this plan still valid?” reviews created when later conversation may conflict with future steps.

Store the user’s decision about whether an earlier plan still applies. This closes the associated review reminder. Update the task separately only when the user chose to change it.

Use when a previously stored future-affecting fact is explicitly replaced by newer information. Keeps history instead of deleting it.

Trace a conversational reminder back to its stored origin: project/node, context signal, plan review, creator/source and timestamps. Use when the user asks "why are you reminding me about this?" or doubts the memory.

Cheap per-turn gate for ambient Fresh Continue behavior. Returns at most one eligible conversational reminder candidate plus the total due count. Call once on each user turn when Fresh Continue is available; do not mark anything surfaced merely by checking.

Read reminder flags that are currently eligible to be mentioned in conversation. This is intentionally topic-independent. Reading does NOT reset a flag. If you actually mention one to the user, call attention_flag_surfaced afterwards. If the user does not answer, leave it active.

Create a persistent conversational flag such as “ask me what happened with X later”. Flags survive unrelated conversations until explicitly resolved, and may be attached to a project/node or be global.

Call ONLY after the reminder was actually stated to the user in conversation. This starts the cooldown but does not resolve the flag. If the user does not answer, the flag remains active and becomes eligible again later.

Apply the user response to a flag. Use resolve only when complete/not needed; snooze when the user says later; keep leaves it active. No user response means do not call this tool.

Change flag text, importance, cooldown, target project/node or earliest reminder time without closing it.

Use this when the user asks “proje ne alemde?”, “durumu güncelle”, “nerede kaldık?” or similar. It returns the current roadmap plus workspace/Git evidence and a reconciliation prompt. After reading it, inspect the actual workspace with your available tools, update stale nodes with task…

Return a concise human-readable summary of progress, active work, ready work and blockers.

Generate a comprehensive prompt that another AI/session can use to continue exactly where the project stopped.

Read recent audit events to understand what changed and in which order.

Very lightweight per-turn check for due conversational reminders or pending plan confirmations when the local PC may be offline.

Shows whether the local Fresh Continue PC has recently synced and how many offline events are waiting.

Use only when a concrete statement can affect a future plan while the local Fresh Continue MCP is unavailable. The event will reconcile into the local app when the PC returns.

Create a conversational reminder in the always-on relay while the local PC is unavailable. It becomes usable immediately and syncs to the local Fresh Continue app later.

Call only after you actually mention a relay reminder to the user. Starts its cooldown and queues the same state for local sync.

Resolve, snooze or keep an ambient relay reminder while the PC is offline; the action is later applied to local Fresh Continue too.