Teams and projects

Tool calls need to know two things besides who you are: which team's wallet to bill, and which project's data they're working with. That's team and project context.

Teams

A team is a billing and membership unit: one shared wallet, one slug, members with roles. Tool calls made with team context bill the team wallet; calls made without it bill your personal wallet. See Create a team.

Projects

A project is the unit your working data belongs to — ingested log events, incident groups, entity relations. The three project-scoped research tools (search_logs_temporal, query_temporal_relations, investigate_incident) operate on that data, which is why they require project context.

Where context lives

In a UE project, the durable form of both contexts is the engine's own Project Settings — the Spaghetti section of Config/DefaultGame.ini:

[/Script/Spaghetti.SpaghettiProjectSettings]
TeamId=uuid-of-your-team
ProjectId=uuid-of-your-project
; plus TeamName, ProjectName, ApiBaseUrl, McpUrl — display and endpoint hints

You normally never touch this file directly: it's visible in the editor under Edit → Project Settings → Plugins → Spaghetti, and the wiring paths below write it for you. Three things worth knowing:

• It's context, not credentials — ids and display names only, no secrets; a normal engine config file, safe to commit to Git or Perforce.
• One settings section per project directory is what lets two clients work on two projects of the same team at once — each carries its own context.
• The context reaches the Workbench as x-spaghetti-team and x-spaghetti-project headers on every call, configured in your AI client. Without them you work on your personal account — everything works except the three project-scoped research tools.

The context is wired for you — see Connect your AI client:

• Ask your AI client to run setup_spaghetti — it picks or creates the team and project with you, then writes the settings and the client config.

Next steps

• Create a team
• Connect your AI client