Skip to content
Wire Docs

Container Best Practices

This guide covers best practices for organizing context containers.

Planning Your Containers

Section titled “Planning Your Containers”

Before creating containers, consider:

  1. Scope - What context belongs together?
  2. Access - Who needs access to this context?

Naming Conventions

Section titled “Naming Conventions”

Use concise, descriptive names:

  • “Product Documentation”
  • “Customer Support Scripts”
  • “Engineering Standards”

Organization Patterns

Section titled “Organization Patterns”

By Project

Section titled “By Project”

One container per project or product:

my-org/
├── web-app-docs
├── mobile-app-docs
└── api-specs

By Team

Section titled “By Team”

One container per team or department:

my-org/
├── engineering
├── design
└── customer-success

By Content Type

Section titled “By Content Type”

One container per content type:

my-org/
├── documentation
├── research-data
└── meeting-notes

Common Mistakes

Section titled “Common Mistakes”

Too Many Small Containers

Section titled “Too Many Small Containers”

Problem: Creating a container for each document.

Solution: Group related documents in one container. With too many small containers, you lose the benefits of preprocessing—entities within data aren’t linked across containers, so your agent has to build that context at query time.

Too Few Large Containers

Section titled “Too Few Large Containers”

Problem: Putting everything in one container.

Solution: Separate by topic or access needs. Purpose-driven containers offer more contextual tools, making it easier for your agent to execute and saving tokens.

Next Steps

Section titled “Next Steps”