---
name: weget-workspace
description: Use Weget as a persistent workspace for notes, folders, projects, tasks, proactive focus, linked documents, and verified Finish Mode.
---

# Weget Workspace

Treat Weget as the persistent system of record around the current coding or knowledge-work session. Keep the interaction natural: use the workspace silently when the user's intent is clear, and surface only decisions that need confirmation.

## Connect

- MCP endpoint: `https://creaverse.art/api/mcp`
- Server name: `weget`
- Read the token only from `WEGET_API_KEY`.
- Never put the secret in prompts, URLs, repositories, logs, or shared configuration.

See the complete installation guide at `https://creaverse.art/mcp-install.md`.

## Start with context

1. Call `weget_workspace_overview` when a request may depend on prior notes, tasks, or projects.
2. Pass a concise query describing the current work.
3. Use `weget_search_notes` only when the overview is insufficient.
4. Do not request private context unless it is needed and the user granted `mcp:private`.

Do not claim that Weget remembers something unless the relevant tool returned it.

## Connect work to projects

1. Call `weget_resolve_project` before automatically linking new work.
2. Link directly when the decision is `auto`.
3. Offer the best candidates when the decision is `suggest`.
4. Leave the item unlinked when the decision is `none`, unless the user chooses a project.
5. Preserve explicit project IDs.

Create a project when the user starts a durable stream of work with a goal and expected deliverables.

## Manage tasks

- Create a planned task for an explicit promise, deadline, or request to track work.
- Create a proposed task with `needs_confirmation=true` when a task is inferred.
- Store the reason in `agent_reason`.
- Link source notes and project references whenever possible.
- Move status only when supported by user input or verified evidence.
- Use `waiting` when progress depends on a person or external event.
- Mark `done` only when the outcome is actually complete.
- Confirm before cancelling.

## Create notes and documents

Use `weget_create_note` for durable knowledge, decisions, meeting notes, reusable plans, and results. Use `weget_create_task_artifact` for a checklist, brief, report, or working note belonging to one task.

Do not overwrite substantial note content without first reading it. Avoid duplicates by searching before creating.

## Use Finish Mode

Use Finish Mode only when the user asks the agent to carry an accepted task to a concrete, verified outcome.

1. Make the outcome explicit.
2. Define observable completion criteria.
3. Start with `safe_internal` unless the user requests another policy.
4. Record progress and evidence with `weget_update_finish_mode`.
5. Request approval before risky, external, destructive, financial, or irreversible actions.
6. Complete only when every required criterion is satisfied and supported by evidence.

## End coherently

Before handing off substantial work:

1. Update the linked task and its next step.
2. Save durable decisions or results.
3. Add evidence for completed Finish Mode criteria.
4. Report what changed in Weget in one compact summary.

Read `tools.md` for the exact tool map and scope behavior.