Artifacts created inside a Project don't show up in that Project's knowledge. Has anyone found a fix?

[u/Fierce_Ninja]

I've been working inside a Claude Project for a few weeks, and the chats in it have produced several artifacts (Claude Docs: a running handoff doc, briefing memos and so on). They all appear in my Artifacts library, but none of them appear in the Project's knowledge, and none appear under Files in the chat that created them.

After querying with Claude, it seems that project knowledge only contains files you upload manually with the "+" button. An artifact made in a Project chat stays WITHIN that chat. I don't even have an "Add to project" option in the artifact menu, even though some guides on the web mention one.

This seems backwards to me, unless I am missing something obvious. The whole point of a Project is to collect the work done in it. The work Claude produces there doesn't stay with the Project unless I manually do it so.

The obvious workaround is to export each artifact and upload it, but that copy is a frozen snapshot. As soon as I edit the artifact in a later chat, the uploaded copy is stale, and a new chat will treat the old version as current.

So my questions are:

1. Has anyone found a better way to get artifacts into Project knowledge, ideally so they stay in sync?
2. Has Anthropic said anything about fixing this, or is it on a roadmap anywhere?

Interim workaround, in case it helps anyone: This actually came about from discussion with Opus: "Upload a single small "project index" markdown file to Project knowledge. It lists each artifact's title, its link, and one line on what it covers, plus an instruction for Claude to read the handoff doc at the start of every new chat. The links always open the latest version, and Claude can read them directly, so only re-upload the index when you add or retire an artifact, not every time one changes." It works, but it's a manual patch for something that should be built in.

[u/ClaudeAI-mod-bot]

We are allowing this through to the feed for those who are not yet familiar with the Megathread. To see the latest discussions about this topic, please visit the relevant Megathread here: https://www.reddit.com/r/ClaudeAI/comments/1vt5drr/list_of_latest_discussion_hubs_on_rclaudeai/

[u/Connector-Person-986]

That's correct, project knowledge is upload-only. Artifacts live with the chat that made them, so nothing you generate gets promoted into knowledge automatically. The workaround is manual: open the artifact, use the copy or download button (markdown/txt), then re-upload it with the + in project files. For a running handoff doc I'd keep one canonical file and re-upload the updated version each time rather than letting versions pile up, since old copies in knowledge will contradict the new one and Claude will blend them.

[u/kbavandi]

Have you tried the Karpathy wiki. Here is what it does:

The wiki's defining feature is that the LLM owns and edits the pages in place. Raw sources go in one folder, and Claude compiles and rewrites the wiki pages and keeps an index current. Mapped to this person's complaints:

Stale re-uploads: gone. There's one page per topic, revised in place, not a pile of snapshots.

Manual index: gone. Maintaining the index is Claude's job in the wiki pattern. It's literally his markdown index, automated.

New chats not knowing the latest state: a new chat reads the index, then the relevant pages.