Skip to main content

How Pip uses project context

Discover how Pip leverages your project information for smarter suggestions.

One of Pip's most powerful features is its ability to leverage your project's context. This means that when you interact with Pip within a specific project, it doesn't start from a blank slate; instead, it uses the information it already knows about your project to provide more relevant and accurate assistance.
​

What Constitutes Project Context?

Pip draws information from various aspects of your project, including:

  1. Project Details: The project's title, type, product description, target indication, geography, and other core information you've defined are all used by Pip to understand the overarching goals and scope.

  2. Current Stage: Pip understands which stage your project is currently in (e.g., "Research & Discovery," "Development"). This helps it tailor its responses and suggestions to the current phase of your work.

  3. Project ReadMe / AI Instructions: Many projects have a dedicated "Project Context" area where you can provide a Project ReadMe or specific instructions for AI interactions. This allows you to give Pip tailored guidelines, key terminology, or preferred approaches for your project.

  4. Existing Documents and Research Assets: Depending on its configuration, Pip can access previously generated documents, research findings, and other assets within your project's vault. This enables it to build upon existing knowledge and avoid redundant work.

  5. Conversation History: If you're continuing a conversation within a project, Pip remembers previous exchanges, ensuring continuity and allowing you to build on prior discussions without repeating yourself.

How Context Enhances Your Interactions:

  • More Relevant Responses: When you ask a question like "What are the key regulatory hurdles?", Pip can automatically infer that you mean "key regulatory hurdles for this specific project's product type and target market."

  • Tailored Suggestions: If you're in the "Research & Discovery" phase, Pip might suggest specific research toolkits. If you're in "Development," it might focus on drafting technical specifications.

  • Reduced Need for Repetition: You don't have to constantly remind Pip about your project's fundamentals.

  • Improved Document Generation: When generating documents, Pip can pull in relevant project details, ensuring the output aligns with your project's specifications.

Best Practices for Maximizing Context:

  • Keep Project Details Updated: Ensure your project's title, description, and other core details are accurate.

  • Utilize Project Context/ReadMe: Provide clear, concise instructions or a ReadMe in the project settings to guide Pip.

  • Work Within Projects: For project-specific tasks, always interact with Pip from within the relevant project environment.

By leveraging your project's context, Pip becomes an even more powerful and integrated partner in your innovation journey, understanding your needs and providing truly intelligent assistance.

Did this answer your question?