Attaching Context Packs to AI Sessions

Overview

In a modern engineering organization, the primary challenge is not a lack of information, but the erosion of context. As teams scale and projects evolve, the reasoning behind critical technical choices often evaporates, leading to architectural drift and repeated mistakes. Hopsule addresses this through Context Packs—portable bundles of accepted decisions and append-only memories. This article provides an exhaustive guide on how to attach these Context Packs to your AI sessions, ensuring that your AI assistants, such as Hopper, and external agents connected via Hopsule MCP, operate with the full authority of your organization’s judgment.

Attaching a Context Pack is the act of making your organizational memory active and enforceable. It transforms a passive record of the past into a living constraint for the present. Whether you are using the Hopsule Dashboard, the Hopsule CLI, or the Hopsule IDE Extension, the process of context attachment is the bridge between historical reasoning and future execution.

Prerequisites

Before you can attach Context Packs to your AI sessions, ensure the following requirements are met:

• Active Hopsule Account: You must have an active account with access to at least one Organization and Project within the Hopsule Dashboard.

• Accepted Decisions: Context Packs are most effective when they contain decisions that have transitioned from Draft or Pending to the Accepted state. Only Accepted decisions are surfaced as enforceable constraints.

• Configured Context Packs: You must have created at least one Context Pack (Capsule) and populated it with relevant decisions and memories.

• Tool Installation: If you are using external AI agents, ensure Hopsule MCP is installed and configured. For IDE-based enforcement, ensure Hopsule for VS Code is active in your environment.

• Authentication: Ensure you are authenticated via the Hopsule CLI or the Hopsule Dashboard to allow secure token exchange for context retrieval.

Managing the Context Pack Lifecycle

To understand how to attach context, you must first understand the state of the context you are attaching. Context Packs within Hopsule follow a specific lifecycle that dictates their availability to AI sessions:

• Draft: The pack is being assembled. It is not yet available for attachment to production AI sessions.

• Active: The pack is ready for use. It can be attached to Hopper, Hopsule MCP, and the Hopsule IDE Extension.

• Frozen: The pack is locked for audit or compliance purposes. It can still be read by AI agents but cannot be modified.

• Historical: The pack is deprecated. It remains in the Hopsule Dashboard for traceability but is hidden from active AI session suggestions.

Attaching Context Packs in the Hopsule Dashboard

The Hopsule Dashboard serves as the central command for managing your organizational memory. Attaching context here primarily affects Hopper, the built-in advisory AI assistant.

1. Log in to the Hopsule Dashboard and select your project from the organization selector.

2. Navigate to the Context Packs (or Capsules) tab in the left-hand navigation menu.

3. Locate the specific Context Pack you wish to use. Ensure its status is set to Active.

4. Click on the Hopper icon in the bottom-right corner of the dashboard to open the chat interface.

5. Within the Hopper interface, click the Attach Context button (represented by a capsule icon).

6. A list of available Context Packs will appear. Select one or more packs by clicking the checkbox next to their names.

7. Once selected, click Apply Context. Hopper will now acknowledge the specific decisions and memories contained within those packs for the duration of the session.

8. To verify the attachment, you can ask Hopper: "Which decisions are currently guiding this session?" Hopper will list the active decisions and the reasoning (memories) linked to them.

Enabling Context Awareness via Hopsule MCP

Hopsule MCP (Model Context Protocol) is the primary mechanism for bringing your team's decisions into external AI tools like Cursor, Claude Desktop, or custom-built agents. This allows these agents to become "decision-aware" automatically.

1. Open your terminal and ensure you are logged in via the Hopsule CLI using hopsule auth login.

2. Navigate to the Hopsule Dashboard and go to the Settings section of your Context Pack.

3. Locate the MCP Integration section and copy your Session Token. This token is unique to your user and project context.

4. Configure your external AI agent to point to the Hopsule MCP server. In most tools, this involves adding the Hopsule MCP endpoint to your configuration file.

5. When the AI agent initializes the connection, Hopsule MCP automatically provides the agent with a read-only view of all Accepted decisions and Memories within the Context Packs associated with your active session.

6. Unlike the dashboard, Hopsule MCP handles context attachment dynamically based on the project root. If your project contains a .hopsule configuration file, Hopsule MCP will automatically attach the Context Packs specified in that file.

Using Context Packs in Hopsule for VS Code

The Hopsule IDE Extension provides the most direct form of enforcement. It doesn't just inform an AI; it surfaces contradictions in real-time as you or your AI agent writes code.

1. Open VS Code or Cursor and ensure the Hopsule for VS Code extension is installed.

2. In the primary sidebar, click on the Hopsule icon to open the decision tree view.

3. Click the Context Packs folder to see a list of packs available to your current workspace.

4. To attach a pack, hover over the pack name and click the Activate (lightning bolt) icon. This tells the extension to monitor your active editor for any code that contradicts the decisions in that pack.

5. If you are using an AI agent within the IDE (like Cursor's Composer), the extension will provide the attached context to the agent's prompt context automatically.

6. When a contradiction is detected, a warning will appear in the Problems tab and as a squiggly underline in your code. You can hover over this to see the specific decision being violated and the memory explaining why that decision exists.

Sharing Context via Public Tokens

Sometimes you need to attach context to a session involving external stakeholders or temporary contributors who do not have full access to your Hopsule Organization.

1. In the Hopsule Dashboard, select the Context Pack you wish to share.

2. Click the Share button in the top-right corner.

3. Toggle Enable Public Access. This generates a secure, read-only token.

4. Choose the Expiration for this context attachment (e.g., 24 hours, 7 days, or No Expiration).

5. Copy the Context URL or Public Token.

6. An external user can use this token in their own Hopsule CLI or Hopper session to temporarily attach your team's decisions to their environment. This ensures they follow your governance standards without needing a permanent seat in your organization.

Tips and Best Practices

• Granularity Matters: Instead of one massive Context Pack for the entire company, create smaller, focused Capsules for specific domains (e.g., "Frontend Architecture," "Security Protocols," "Deployment Standards"). This prevents the AI from being overwhelmed with irrelevant context.

• Leverage the Knowledge Graph: Before attaching a pack, use the Knowledge Graph (the Brain) in the Hopsule Dashboard to visualize how decisions are linked. This helps you identify if you need to attach multiple related packs to get the full picture.

• Freeze for Compliance: When a project reaches a major milestone or enters maintenance mode, transition its Context Pack to Frozen. This ensures that the decisions guiding the AI sessions for that project remain a "point-in-time" reference, which is critical for long-term maintenance.

• Use Memories for "The Why": Decisions are the "What," but Memories are the "Why." Always ensure your Context Packs include the relevant Memories. An AI agent is much more effective when it understands the history and lessons that led to a decision, rather than just the decision itself.

• Advisory vs. Enforceable: Remember that Hopper is advisory. It will suggest improvements based on context. If you need strict enforcement, rely on Hopsule for VS Code, which surfaces warnings directly in the workflow.

• Regularly Deprecate: If a decision is no longer valid, move it to the Deprecated state. Hopsule will automatically stop surfacing it in active Context Packs, preventing your AI tools from hallucinating outdated constraints.

Troubleshooting

Related Articles

• Managing Decision Lifecycles: From Draft to Deprecated

• Visualizing Relationships with the Knowledge Graph

• Setting Up Hopsule MCP for External AI Agents

• Creating Your First Context Pack (Capsule)

By effectively attaching Context Packs to your AI sessions, you move beyond simple automation and into the realm of decision-aware engineering. Hopsule ensures that your AI tools do not just generate code, but generate code that respects the hard-won wisdom of your organization. Remember: Enforcement is remembrance, not control. By providing your AI with the right context, you are ensuring that your team's most important decisions are never forgotten.