Browse

Read a project card from the knowledge vault: type, status, next step, updated date, and the places on disk it covers (repo, folder, workflow). Cards are the only home of status. Without a name, returns the working directory's project card (created on first use).

Set a card's status and/or next step and stamp its updated date. This is the only place status and the next step are written: never put them in a note. Without a name, updates the working directory's project card (created on first use). Status archived moves the project folder to archive/. add_search_folder links a folder outside the project (docs, a shared library) so recall and search_local cover it too, and indexes it.

Save a new note in the knowledge vault: one idea per note, with frontmatter (type, status, created, summary, tags, links). Refuses a title that already has a note - one home per fact, so edit that note instead. Use for a decision, a gotcha, a concept or a tool worth remembering beyond this session; it goes in the project's folder unless scope says otherwise. Status and next steps go to the card instead.

Find the notes in the knowledge vault related to a query, by walking the vault's link graph from the words of the query (no model involved). Returns note paths with their one-line summaries, best first, within a small token budget. Each turn already carries a recall for the user's request; call this to look up something else (a project, a decision, an error). Then read only the notes you need with read_file.

Delete a memory entry by key. Use to remove outdated or incorrect facts from persistent memory.

Run a relational query over agent state. Relations: `memory` (persistent memory entries: key, value, namespace, type, references, createdAt, updatedAt), `tool_calls` (recent tool call history: name, args, result, timestamp), `tasks` (active goal's task list: id, desc, status, rounds, note). Query language is expr-lang: filter(relation, predicate) selects rows (e.g. filter(memory, .type == "error")), map(relation, expr) projects fields, join(left, right, leftField, rightField) equi-joins two relations into rows with left_/right_ prefixed fields, union(a, b) combines two relations with set semantics. String operators are infix: .value contains "x", .value startsWith "x", .value endsWith "x", .value matches "regex"; lower()/upper() are functions (lower(.value)); membership is .key in ["a", "b"].

Save a fact to persistent memory. The memory is injected into every LLM call automatically. Use for project conventions, user preferences, key decisions, or any information that should persist across sessions. Keys should be short and descriptive.

Search persistent memory for entries matching a query. Returns up to 20 matching key-value pairs (each value capped), best match first: a key hit outranks a value-only hit, more query words outrank fewer, and a newer update breaks a tie. Use to recall previously saved facts, preferences, or decisions. There is no memory_list tool; the memory graph is already in the system prompt.