GetSpace

Replace the text of one memory claim, using its current IDs. resource_id is the memory record and entry_id is the claim; read both, with the current revision and value, from list_memories first. The new value, at most 2,000 characters, is re-indexed through the configured providers, and the previous text remains in the earlier immutable revision. Never replace a user correction without their request. Reuse command_id unchanged on retry.

edit_memory_claim

Permanently remove one claim from a memory and keep its other claims. resource_id is the memory record and entry_id is the claim; read both, with the current revision, from list_memories first. The claim leaves the index at once, so recall stops returning it. This is not a reversible exclusion, though its text remains in the earlier immutable revision. To remove a whole memory record, use delete_memory. Reuse command_id unchanged on retry.

forget_memory_claim

Identify this connection, then send its stable Agent ID on every content request. With no arguments, discover the identity already selected on the website. Reuse an existing agent_id for another connection. Or supply a name and harness (codex, claude-code, hermes, claude, chatgpt, cursor, gemini, pi, openclaw, prime-agent, opencode, cline, devin, factory, grok, perplexity, deepseek, zai, meta, minimax, kimi, other). Matching names and harnesses reuse one identity. Names are attribution, never credentials. Set X-Space-Agent-ID in client headers for automatic sending, or include agent_id in each tool call. Only the owner can rename identities or reassign an already identified connection.

identify_agent

List this Space's saved agent identities to reuse one when connecting.

list_agent_identities

List up to 50 documents or tasks; use next_cursor to continue. Memory is never listed here: a generated memory is read with list_memories and a handoff through get_context with mode='resume'.

list_resources

Read current memory claims with their source and revision, newest first. Pass a query to search every memory in the Space, ranked by how rare each matched word is; a search returns its best matches and no cursor. Without a query, follow next_cursor to page through the Space. Excluded memory resources are also listed, with recall.excluded=true, but cannot be recalled. Stale memory is flagged and remains recallable unless excluded. To change one claim, use edit_memory_claim, forget_memory_claim, classify_memory_claim or route_memory_claim.

list_memories

Parameters: Space ID and optional agent identity. What it does: lists configured task status values and display labels. Output: column revision and ordered columns, including custom statuses.

task_columns

Parameters: Space, item kind, optional cursor and deleted state. What it does: lists projects, folders, databases, categories, sections or skills. Databases are listed with their schema and record_count, never their records: read rows with read_database and change them with query_database. Skills are listed with name, description, warnings, paths and bytes, never their file text: read one with get_workspace_item. Output: one page of items; follow next_cursor for the complete list.

list_workspace_items

Parameters: optional subscription_id or database_id filter and limit (1-50). What it does: leases the oldest waiting database change events from this Space's agent inbox for ten minutes, so another agent pulling at the same time does not receive them. The Space owner creates an inbox subscription under Settings → Webhooks, choosing a database and optionally one select transition such as Stage → Review. Each item carries a stable delivery_id and the event: database_id, record_id, operation, revisions, changed field IDs and, for a filtered subscription, the before/after values of that one field. Read the current record with read_database before acting; the event is a hint, not the record. Call ack_events with each delivery_id once the work is done; an unacknowledged lease returns to the queue, and after five pulls without acknowledgement the delivery fails and the owner can redeliver it. Requires a write grant held by the Space owner. Poll on a schedule; nothing pushes to the agent. Output: items, has_more, lease_seconds.

pull_events

Read a document or task, optionally at an immutable historical revision. A document with a `file` field keeps an original file the person uploaded on the website, such as a PDF, Word document, presentation, picture or video. Its body holds the text extracted from that file; a picture or video has none, so its title is what describes it. `file` gives the name, media type, size, digest and part count, a picture's or video's dimensions and a recording's duration when the browser read them, and the details of the thumbnail the website shows. The file itself is viewed and downloaded on the website and cannot be read through this tool.

get_resource

Parameters: Space, item ID, optional historical revision and install. What it does: reads a project, folder, database, category, section or skill. A database comes with its schema and record_count, never its records: read rows with read_database and change them with query_database. A skill carries its files as path and text, SKILL.md first. A skill read counts as a use of it; install=true counts it as an install instead, for a copy written into an agent's skill folder. Output: the item and its revision.

get_workspace_item

Parameters: Space, database item ID and a SQL read. What it does: runs SQLite SELECT on one table named records, with columns id, name, notes, created_at, updated_at and one column per field, named after the field (quote names with spaces). Send sql with params bound to ? placeholders, or a statements batch of up to 20. Reads the current revision and never changes it: INSERT, UPDATE and DELETE are refused. Checkbox columns hold 0 or 1. include_schema returns the column map. Output: results per statement and the revision read.

read_database

Parameters: Space, memory resource ID, and limit from 1 to 50. What it does: reads outgoing node links and reverse backlinks. Explicit links survive content edits; inferred links depend on assessed endpoint text. Deleted/excluded nodes are hidden; source-stale inferred links are hidden. Origin is explicit or inferred. These pointers are not proof of an answer. Output: links, backlinks and has_more, without model calls.

get_memory_links

Parameters: Space and optional max_chars (4,000-20,000, default 12,000). What it does: returns where things belong. Sections hold projects, folders and databases; projects hold their folders and databases. Databases show fields and record_count, never records. A task database also shows tasks: its status and planned field names and the statuses that count as done; query its open rows by planned day for the user's daily work. Routing rules learned from memory sit on the container they govern, plus Space-wide global_rules. skills lists the Space's skills by name and description; a shortened map gives only skill_count. Call it at the start of substantive work and before creating a project, folder, database or document. Rules guide placement and never override the user. Output: the bounded map; truncated=true means descriptions or rules were shortened, never that a container was hidden. No model calls.

get_space_map

Parameters: Space, recall request, agent identity and optional numeric timings. What it does: recalls cited, currently permitted context. Use mode='resume' for recent handoffs. mode='search' requires a query. strategy='auto' combines exact per-Space vector candidates and lexical sources, then assesses support with the configured model. 'lexical' makes no model calls; 'prompt' adds Memora's iterative policy before the evidence assessment. Model calls use the configured provider. For a startup brief use mode='resume', compact=true: long handoffs reserve excerpt space for next actions, unresolved questions, decisions and progress. Compact resume makes no model calls; open cited revisions for complete text. Defaults: limit=5, max_chars=12000. Maxima: limit=10, max_chars=20000. Results carry verification='memory', 'handoff' or 'user_authored' and a stale flag. Assessed items also carry relevance=direct, historical or conflicting. found=false means no supported answer was found in the retrieved evidence; it does not prove no record exists. A note saying matches did not fit max_chars means retry with a larger max_chars. Pass include_related=true to also receive cue-linked claims in a separate, unranked `related` list. Output: bounded evidence. include_timings adds numeric timings_ms and tool_total_ms; stages can overlap and exclude earlier transport/auth work. Timings contain no content or identifiers. Errors still deny the response.

get_context

Set the containers one memory claim governs as a placement rule. routes_to holds up to 8 container IDs from get_space_map, where what the claim describes belongs. It replaces the claim's current routing; an empty list clears it and pins the clear, so automatic routing leaves the claim alone. Read the IDs and current revision from list_memories first, and reuse command_id unchanged on retry.

route_memory_claim

Parameters: Space, command ID and the complete intended document or task. What it does: creates at revision zero or updates at the current revision. Send kind, title, body, status and intended project, folder, priority and recall metadata. Omitted body/status reset to defaults; omitted project, folder, priority and recall preserve existing values on updates. Explicit project=null or folder=null clears that association. Folders apply only to documents and are independent of projects. New folder assignments must name an active folder in this Space; unchanged archived references may remain. A project must name an existing project in this Space. Kind cannot change. Tasks cannot carry recall.category="handoff". Updating a document that keeps an original file keeps the file; only the website uploads one. Generated memory is never edited here: use remember, remember_claims, extract_memory or edit_memory_claim. Prefer a status from task_columns; a new status value is saved as a column labelled from it (add_task_column picks the label), and set_task_status moves a task without resending its body. Set status "needs_you" on a task when the work cannot continue without the person's decision, approval or merge: it stays on their home page until they change it. Only tasks take it; when a document needs review, save the document, then a needs_you task that names it, and never write a separate "blocked" document. Stay within 1 MiB. Output: the saved resource. Reuse command_id unchanged on retry.

save_resource

Save authored text directly: model organization, embedding, encryption, storage. Memory is autonomous: it is indexed immediately and is available to every authorized agent without human review. This sends your text to the configured embedding provider and the decision model when configured, without text generation. Wording is preserved; text over 2,000 characters is split into bounded claims. A write fails while no memory provider is configured. `importance` is 0 to 3, where 0 means undeclared; use it for constraints, decisions and corrections you expect to matter later. Prefer save_handoff for session context with decisions and next actions, and extract_memory to mine documents or conversations. Optional links connect this node to exact existing memory IDs without model approval; use expands_on for a detail-to-subject connection. When the user states where something belongs, pass routes_to with up to 8 exact container IDs from get_space_map. Reuse command_id unchanged on retry.

remember

Save an explicit session handoff as an encrypted versioned document. Supply decisions, progress, unresolved_questions, next_actions and topics. sources must name existing resource IDs and revisions in this Space. Use a new command UUID per change, and reuse it unchanged on retries.

save_handoff

Parameters: Space, item ID, current revision, command ID, kind and data. What it does: saves a project, folder, database, category, section or skill. Projects use name, description, status and optional section_id. Folders use name, description and optional section_id and project_id; a folder's project places it in the Space map and never moves its documents. New section or project assignments must name an active item in this Space. Categories and sections use name and description; use user-defined labels. Databases use name, description, fields, view, groupBy and optional project_id, section_id, tasks and records. tasks marks the rows as tasks: status is a select field ID, done lists the options that close a row, and planned is a date field ID for the day a row is planned for. Leave records out to change the schema and keep every stored row; change rows with query_database. Pass records only to replace the whole table, such as a bulk import: rows it omits are deleted, and only rows that differ are stored, each as its own encrypted revision. Skills use files: the whole Agent Skills folder as {path, text} entries, with SKILL.md at the top and its YAML front matter giving name and description. name, description and warnings are read from SKILL.md. Text only: 50 files and 512 KiB at most. Names are unique among active skills, and only the Space's owner and their agents change skills. Read the current item first and preserve field IDs. Limits are 30 fields, 10,000 records per database and 2,000 characters per value. Create at revision zero. Output: the saved item, with its record_count for a database, and its new revision.

save_workspace_item

Save already-separated claims verbatim: classify, embed, encrypt, save. Use when the material is already split into claims, each with its own index, type and importance, or when import provenance applies. For one authored fact, preference, decision or user-written memory, including a single sentence, use remember with title and text instead. Each claim carries an index label and its exact wording as value. Classification runs when configured; no extraction or generated cues. A write fails while no memory provider is configured. A claim that says where something belongs may carry routes_to: up to 8 exact project, section, folder or database IDs from get_space_map; it then shows on those containers in the map. Reuse command_id unchanged on retry, and use extract_memory only to mine a document or conversation into claims.

remember_claims

Search full current documents, tasks, memory, projects and database records. Continue using next_cursor and snapshot until next_cursor is null, even when a page has no matches. Each call scans at most 25 items. Restart on snapshot conflict. An optional project filters its documents and tasks.

search_workspace

Parameters: node ID, current revision, command ID and complete explicit links. What it does: replaces intentional node links without an AI judgment. Supply exact target resource IDs and relation related or expands_on; never guess a target from an ambiguous name. Empty links removes explicit connections only. Output: saved memory with links; reverse backlinks are automatic.

set_memory_links

Get the Private Space, Tasks collection, assigned agent_id and skills. Send the returned agent_id with every content call, as a tool argument or the X-Space-Agent-ID header. If null, call identify_agent first. skills lists up to 50 of the Space's active skills by name and short description, and skill_count counts them all; both need an agent_id.

workspace_info

Return non-sensitive build information; does not access a workspace.

server_info

Show the configured memory model provider and models, without secrets.

memory_info

Save an encrypted extraction job and return its ID and status immediately. Supply raw text/title or an existing current source revision. The worker uses the configured provider, and the job is refused while none is configured. Saved input becomes generated memory only when status is ready. Poll memory_job. Closing the session keeps the job; revoking the submitting agent grant stops unfinished work. Reuse command_id.

extract_memory