Cross-Project Artifact Access
Published March 19, 2026 · Last updated March 20, 2026 · 3 min read
Cross-Project Artifact Access
Obvious agents can read artifacts and files from other projects in your workspace — not just the one you're working in. This means you can ask an agent in your current project to pull in a report from Finance, check files in a Marketing project, or analyze a workbook that lives somewhere else, all without leaving your current context.
Three agent tools support cross-project access: explore-artifacts, list-files, and get-file. Each accepts an optional projectId parameter that redirects the lookup to a different project instead of the current one.
How it works
When you ask an agent to access something from another project, it passes the target project's ID to the relevant tool. The system checks whether you have permission to access that project before returning anything. If you do, the agent retrieves the artifact or file and works with it normally. If you don't, it returns nothing — the same response as if the project didn't exist.
You don't need to know the project ID yourself. You can ask the agent by name: "Read the Q4 report from the Finance project" or "List all workbooks in the Marketing project." The agent will locate the project and use the correct ID.
Which tools support it
explore-artifacts — Browse or inspect artifacts in another project.
list-files — List uploaded files in another project.
get-file — Retrieve the content of a specific uploaded file from another project.
Note: Recording artifacts are not accessible cross-project at this time.
Permissions
Cross-project access requires workspace-scoped access to the target project. In practice, this means you need to be a non-guest member of the workspace and the target project must have workspace-level sharing enabled. Projects that are private to their owner or shared only with specific users won't be accessible.
If a project is inaccessible, the tools return a not-found response rather than an error — this prevents workspace enumeration.
Using it in practice
You don't interact with projectId directly. Just describe what you need:
-
"Read the Q4 report from the Finance project"
-
"List all workbooks in the Marketing project"
-
"Get the customer list CSV from the Sales Data project"
-
"Show me the artifacts in the Design System project"
The agent handles the lookup. If the project name is ambiguous or it can't locate the project, it will ask you to clarify.
Troubleshooting
The agent says it can't find the project or artifact. Check that the target project has workspace-level sharing enabled. Projects shared only with specific users or teams won't be accessible cross-project. If you own the target project, open it and confirm the sharing settings allow workspace access.
The agent returns file metadata but no content.
Binary file formats like .xlsx, .docx, or .zip can't be returned as readable content across projects. If you need to work with the data, ask the owner of the source project to export it as CSV or plain text first.
The agent can access some projects but not others. Access is determined per project. A project that's visible to the workspace is accessible; one that's private or team-only may not be, depending on your membership. Check the sharing settings on the specific project you're trying to reach.
Still stuck? Reach out to help@obvious.ai and include the name of the project you're trying to access.