Skip to main content

Context & Mentions

The quality of Tuanjie AI responses depends heavily on what context is available in the current session.

/ and @ in Conversations​

In the Tuanjie AI chat input box:

  • /: Opens the slash command menu to manage Subagents, Skills, MCP, etc. See the full list in Slash Commands and @ Syntax.
  • @: Commonly used in conversation context to specify Subagents (expert agents), delegating tasks to sub-agents in the corresponding domain for execution, rather than having the main agent make generalized inferences.

If you also use Codely CLI, @ can also be used for files and directories, which differs from the usage in IDE conversations—please distinguish between environments.

@ in CLI: Files, Directories, and MCP​

When using Codely CLI in the terminal, you can use @ to directly incorporate local paths or MCP resources into prompts without manually pasting large blocks of code. See syntax and examples in Codely CLI · Referencing Files and Directories.

Key points summary:

  • Single File: @src/Game/Player.cs, etc., includes file content in context; CODELY.md along the relevant directory chain may also be automatically attached.
  • Directory: Provides a structural listing rather than the full text of each file, useful when you want to see the directory structure first, then decide what to ask.
  • MCP: @server:resource format to retrieve data from connected MCP services, requires MCP to be configured in the client first. See MCP Servers for configuration and troubleshooting.

Codebases and "Semantic Understanding"​

Product forms like Tuanjie Cowork emphasize understanding of full repository structure, and actual behavior respects engineering conventions like .gitignore. See Tuanjie Cowork for details.

When you need to search Unity / Tuanjie public repositories and documentation, you can use the online capabilities Code Search, and reference it as a resource in IDE/CLI according to the documentation.

Custom Documentation and External Knowledge​

If you need to mount documentation sites or context providers at the configuration layer, refer to the context and docs sections in the configuration documentation (for advanced configurations like config.yaml). See the full entries in Configuration Reference.