Long-Term Memory

Taskade EVE's long-term memory is a Project in your workspace. It is not an opaque data object.

You can browse, edit, version, and query it through the Public API.

This architecture keeps Taskade memory visible, editable, and reusable.

Table of Contents

• Mental Model - Memory as Projects
• How Taskade EVE Uses Memory
• Agent Memory vs Taskade EVE Memory
• Model Agnosticism
• Inspect and Edit Memory
• API Access
• Privacy and Scoping
• Best Practices
• Related

Mental Model - Memory as Projects

Most AI platforms store memory in a hidden vector database. You cannot see or directly correct the stored memory.

Taskade takes a different approach.

Why this matters:

• Transparency - you see exactly what Taskade EVE remembers.
• Controllability - edit or delete memory blocks like any project content.
• Composability - use memory as an input to automations, agents, or other apps.
• Portability - memory is part of your workspace, not locked in a separate system.

How Taskade EVE Uses Memory

Taskade EVE is the meta-agent of the platform. You talk to it to build apps and orchestrate work.

• Memory persists across sessions. Taskade EVE retains work context after you close and reopen Taskade.
• Memory is workspace-scoped. Each workspace has its own Taskade EVE memory.
• Memory grows automatically. You do not tag entries by hand.
• Taskade EVE runs on the same Workspace DNA (Projects + Agents + Automations) it orchestrates for you.

Agent Memory vs Taskade EVE Memory

Taskade has two distinct memory systems. Both use the same architectural principle (memory-as-Projects). They serve different purposes.

Model Agnosticism

Memory works across every available AI model.

• Persistent memory is not limited to specific models. Every AI agent supports memory on any model that you pick.
• The memory tool is enabled for all frontier models that Taskade offers.
• A model change does not reset an agent's memory. For example, a change from Claude to another model keeps the same memory.

Inspect and Edit Memory

Find the memory project

In your workspace sidebar, look for the project with the "EVE Memory" prefix, or your agent's memory project. The name varies with the creation date.

Edit memory by hand

Open the memory project like any other project. Then use these controls:

• Remove entries that you do not want Taskade EVE to remember.
• Correct facts that Taskade EVE got wrong.
• Add context for information that Taskade EVE did not infer.
• Version the memory (Taskade's version history applies).

Taskade EVE reads the memory project at each interaction. Your edits take effect in the next conversation.

Common cleanup patterns

• After a major project pivot, prune outdated assumptions.
• Before you share a workspace, review Taskade EVE memory for sensitive content.
• Periodically archive resolved context so memory stays focused on current work.

API Access

Because memory is a Project, the Public API can address it.

All calls use the Action API v2 with a Bearer token.

Find the memory project

const headers = {
  Authorization: `Bearer ${process.env.TASKADE_TOKEN}`,
  "Content-Type": "application/json",
};

const res = await fetch("https://www.taskade.com/api/v2/listProjects", {
  method: "POST",
  headers,
  body: JSON.stringify({ spaceId: SPACE_ID }),
});
const { items } = await res.json();
const memory = items.find(p => p.name?.startsWith("EVE Memory"));

Read memory contents

if (memory) {
  const res = await fetch("https://www.taskade.com/api/v2/listBlocks", {
    method: "POST",
    headers,
    body: JSON.stringify({ projectId: memory.id }),
  });
  const { items: blocks } = await res.json();
  console.log("Taskade EVE remembers:", blocks);
}

Attach memory as knowledge to another agent

// Give a specialist agent access to workspace context
await fetch("https://www.taskade.com/api/v2/addKnowledgeProject", {
  method: "POST",
  headers,
  body: JSON.stringify({ agentId: AGENT_ID, projectId: memory.id }),
});

Memory projects use the same blocks, tasks, and metadata schema as other projects. Treat them as frequently read projects.

Privacy and Scoping

• Workspace-scoped. Taskade EVE memory does not leak across workspaces.
• Controlled by workspace members. Anyone with edit access to the workspace can view and modify memory.
• No external service. Memory lives in Taskade's infrastructure, not a third-party vector store.

Exported bundles never include memory. App exports through Bundles or GitHub leave the memory project behind.

exportBundle does not transfer accumulated agent context to the target workspace.

Best Practices

• Let Taskade EVE remember enough to be useful. Do not wipe memory often. Context compounds.
• Prune when context drifts. After a major pivot, review and edit memory.
• Use memory as input to automations. Read memory with the API to personalize triggered automations.
• Scope sensitive information. If you collaborate with external parties, keep confidential context in a dedicated workspace.
• Document memory assumptions in the project. Taskade EVE reads the project, including explicit memory notes.

Related

→ Action API Guide

→ SDK Cookbook

→ Autonomous Agents

→ AI Agents in Learn Taskade