@adminide-stack/yantra-help-browser 12.0.16-alpha.6 → 12.0.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/components/HelpCenterFooter.d.ts.map +1 -1
- package/lib/components/HelpCenterFooter.js +186 -90
- package/lib/components/HelpCenterFooter.js.map +1 -1
- package/lib/components/HelpCenterHeader.d.ts +1 -5
- package/lib/components/HelpCenterHeader.d.ts.map +1 -1
- package/lib/components/HelpCenterHeader.js +123 -69
- package/lib/components/HelpCenterHeader.js.map +1 -1
- package/lib/components/Icons.d.ts +55 -0
- package/lib/components/Icons.d.ts.map +1 -0
- package/lib/components/Icons.js +186 -0
- package/lib/components/Icons.js.map +1 -0
- package/lib/components/Logo.d.ts +1 -2
- package/lib/components/Logo.d.ts.map +1 -1
- package/lib/components/Logo.js +5 -8
- package/lib/components/Logo.js.map +1 -1
- package/lib/components/PageHero.d.ts +9 -0
- package/lib/components/PageHero.d.ts.map +1 -0
- package/lib/components/PageHero.js +47 -0
- package/lib/components/PageHero.js.map +1 -0
- package/lib/components/SearchBar.d.ts +8 -0
- package/lib/components/SearchBar.d.ts.map +1 -0
- package/lib/components/SearchBar.js +262 -0
- package/lib/components/SearchBar.js.map +1 -0
- package/lib/components/SidebarSearch.d.ts +8 -0
- package/lib/components/SidebarSearch.d.ts.map +1 -0
- package/lib/components/SidebarSearch.js +114 -0
- package/lib/components/SidebarSearch.js.map +1 -0
- package/lib/components/navbar/index.d.ts.map +1 -1
- package/lib/components/navbar/index.js +32 -36
- package/lib/components/navbar/index.js.map +1 -1
- package/lib/compute.d.ts +17 -0
- package/lib/compute.d.ts.map +1 -1
- package/lib/compute.js +111 -3
- package/lib/compute.js.map +1 -1
- package/lib/pages/About/index.d.ts +3 -0
- package/lib/pages/About/index.d.ts.map +1 -0
- package/lib/pages/About/index.js +69 -0
- package/lib/pages/About/index.js.map +1 -0
- package/lib/pages/Blog/index.d.ts +3 -0
- package/lib/pages/Blog/index.d.ts.map +1 -0
- package/lib/pages/Blog/index.js +172 -0
- package/lib/pages/Blog/index.js.map +1 -0
- package/lib/pages/BlogPost/index.d.ts +3 -0
- package/lib/pages/BlogPost/index.d.ts.map +1 -0
- package/lib/pages/BlogPost/index.js +209 -0
- package/lib/pages/BlogPost/index.js.map +1 -0
- package/lib/pages/Careers/index.d.ts +3 -0
- package/lib/pages/Careers/index.d.ts.map +1 -0
- package/lib/pages/Careers/index.js +78 -0
- package/lib/pages/Careers/index.js.map +1 -0
- package/lib/pages/CategoryCollection/index.d.ts.map +1 -1
- package/lib/pages/CategoryCollection/index.js +86 -80
- package/lib/pages/CategoryCollection/index.js.map +1 -1
- package/lib/pages/Community/index.d.ts +3 -0
- package/lib/pages/Community/index.d.ts.map +1 -0
- package/lib/pages/Community/index.js +72 -0
- package/lib/pages/Community/index.js.map +1 -0
- package/lib/pages/Contact/index.d.ts +3 -0
- package/lib/pages/Contact/index.d.ts.map +1 -0
- package/lib/pages/Contact/index.js +128 -0
- package/lib/pages/Contact/index.js.map +1 -0
- package/lib/pages/GetStarted/components/ExampleCard.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/GetStartedHero.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/InfoSection.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/TipCard.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/UseCase.d.ts.map +1 -1
- package/lib/pages/GetStarted/index.d.ts.map +1 -1
- package/lib/pages/GetStarted/index.js +333 -713
- package/lib/pages/GetStarted/index.js.map +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.d.ts +2 -0
- package/lib/pages/HelpCenter/components/HelpCategoryCard.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js +154 -68
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js.map +1 -1
- package/lib/pages/HelpCenter/components/Icons.d.ts +10 -0
- package/lib/pages/HelpCenter/components/Icons.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/Icons.js +338 -78
- package/lib/pages/HelpCenter/components/Icons.js.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.d.ts +3 -0
- package/lib/pages/HelpCenter/components/PopularArticle.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.js +22 -37
- package/lib/pages/HelpCenter/components/PopularArticle.js.map +1 -1
- package/lib/pages/HelpCenter/index.d.ts.map +1 -1
- package/lib/pages/HelpCenter/index.js +261 -44
- package/lib/pages/HelpCenter/index.js.map +1 -1
- package/lib/pages/HelpCenter/mockData.d.ts +16 -0
- package/lib/pages/HelpCenter/mockData.d.ts.map +1 -1
- package/lib/pages/HelpCenter/mockData.js +83 -12
- package/lib/pages/HelpCenter/mockData.js.map +1 -1
- package/lib/pages/LandingPage/components/ArticleCard.d.ts +2 -2
- package/lib/pages/LandingPage/components/ArticleCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ArticleCard.js +31 -20
- package/lib/pages/LandingPage/components/ArticleCard.js.map +1 -1
- package/lib/pages/LandingPage/components/Assets.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/CategoriesSection.d.ts +2 -1
- package/lib/pages/LandingPage/components/CategoriesSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/CategoriesSection.js +33 -23
- package/lib/pages/LandingPage/components/CategoriesSection.js.map +1 -1
- package/lib/pages/LandingPage/components/CategoryCard.d.ts +1 -1
- package/lib/pages/LandingPage/components/CategoryCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/CategoryCard.js +35 -13
- package/lib/pages/LandingPage/components/CategoryCard.js.map +1 -1
- package/lib/pages/LandingPage/components/FeaturedSection.d.ts +2 -1
- package/lib/pages/LandingPage/components/FeaturedSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/FeaturedSection.js +24 -9
- package/lib/pages/LandingPage/components/FeaturedSection.js.map +1 -1
- package/lib/pages/LandingPage/components/HeroSection.d.ts +1 -7
- package/lib/pages/LandingPage/components/HeroSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/HeroSection.js +108 -40
- package/lib/pages/LandingPage/components/HeroSection.js.map +1 -1
- package/lib/pages/LandingPage/components/ResourceCard.d.ts +1 -1
- package/lib/pages/LandingPage/components/ResourceCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ResourceCard.js +24 -19
- package/lib/pages/LandingPage/components/ResourceCard.js.map +1 -1
- package/lib/pages/LandingPage/components/ResourcesSection.d.ts +2 -2
- package/lib/pages/LandingPage/components/ResourcesSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ResourcesSection.js +28 -14
- package/lib/pages/LandingPage/components/ResourcesSection.js.map +1 -1
- package/lib/pages/LandingPage/index.d.ts.map +1 -1
- package/lib/pages/LandingPage/index.js +189 -130
- package/lib/pages/LandingPage/index.js.map +1 -1
- package/lib/pages/Markdown/MarkdownPageLayout.d.ts +3 -0
- package/lib/pages/Markdown/MarkdownPageLayout.d.ts.map +1 -0
- package/lib/pages/Markdown/MarkdownPageLayout.js +318 -0
- package/lib/pages/Markdown/MarkdownPageLayout.js.map +1 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.d.ts +9 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.d.ts.map +1 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.js +65 -0
- package/lib/pages/Markdown/MarkdownPageWithParams.js.map +1 -0
- package/lib/pages/Markdown/index.d.ts +3 -0
- package/lib/pages/Markdown/index.d.ts.map +1 -0
- package/lib/pages/Markdown/index.js +5 -0
- package/lib/pages/Markdown/index.js.map +1 -0
- package/lib/pages/Privacy/index.d.ts +3 -0
- package/lib/pages/Privacy/index.d.ts.map +1 -0
- package/lib/pages/Privacy/index.js +449 -0
- package/lib/pages/Privacy/index.js.map +1 -0
- package/lib/pages/ReleaseNotes/index.d.ts +3 -0
- package/lib/pages/ReleaseNotes/index.d.ts.map +1 -0
- package/lib/pages/ReleaseNotes/index.js +61 -0
- package/lib/pages/ReleaseNotes/index.js.map +1 -0
- package/lib/pages/StatusPage/index.d.ts +3 -0
- package/lib/pages/StatusPage/index.d.ts.map +1 -0
- package/lib/pages/StatusPage/index.js +85 -0
- package/lib/pages/StatusPage/index.js.map +1 -0
- package/lib/pages/Terms/index.d.ts +3 -0
- package/lib/pages/Terms/index.d.ts.map +1 -0
- package/lib/pages/Terms/index.js +60 -0
- package/lib/pages/Terms/index.js.map +1 -0
- package/lib/routes.json +138 -1
- package/lib/templates/content/account-management/account-setup.md +83 -0
- package/lib/templates/content/account-management/delete-account.md +81 -0
- package/lib/templates/content/account-management/preferences.md +98 -0
- package/lib/templates/content/account-management/privacy-settings.md +94 -0
- package/lib/templates/content/account-management/profile-settings.md +78 -0
- package/lib/templates/content/ai-employees/ai-employees-overview.md +97 -0
- package/lib/templates/content/ai-employees/getting-started-ai-employees.md +119 -0
- package/lib/templates/content/ai-employees/how-ai-employees-work.md +123 -0
- package/lib/templates/content/ai-employees/supervised-mode.md +141 -0
- package/lib/templates/content/blog/how-yantra-browser-automates-workflows.md +120 -0
- package/lib/templates/content/blog/introducing-yantra-browser.md +90 -0
- package/lib/templates/content/blog/yantra-browser-productivity-tips.md +98 -0
- package/lib/templates/content/browser-extension/browser-extension-overview.md +60 -0
- package/lib/templates/content/browser-extension/extension-security.md +126 -0
- package/lib/templates/content/browser-extension/getting-started-extension.md +96 -0
- package/lib/templates/content/browser-extension/how-it-works.md +112 -0
- package/lib/templates/content/browser-extension/troubleshooting-extension.md +138 -0
- package/lib/templates/content/browser-extension/use-cases-workflows.md +123 -0
- package/lib/templates/content/content-manifest.json +6245 -0
- package/lib/templates/content/data-privacy/data-collection.md +78 -0
- package/lib/templates/content/data-privacy/privacy-policy.md +100 -0
- package/lib/templates/content/data-subject-privacy/data-access.md +90 -0
- package/lib/templates/content/data-subject-privacy/data-portability.md +97 -0
- package/lib/templates/content/data-subject-privacy/privacy-requests.md +95 -0
- package/lib/templates/content/file-uploads/file-upload-overview.md +93 -0
- package/lib/templates/content/getting-started/getting-started-guide.md +88 -0
- package/lib/templates/content/integrations/crm-integrations.md +130 -0
- package/lib/templates/content/integrations/github-integration.md +95 -0
- package/lib/templates/content/integrations/integrations-overview.md +142 -0
- package/lib/templates/content/integrations/monitoring-integrations.md +109 -0
- package/lib/templates/content/integrations/productivity-integrations.md +129 -0
- package/lib/templates/content/integrations/slack-integration.md +79 -0
- package/lib/templates/content/openclaw/openclaw-architecture.md +202 -0
- package/lib/templates/content/openclaw/openclaw-contribution.md +107 -0
- package/lib/templates/content/openclaw/openclaw-overview.md +152 -0
- package/lib/templates/content/platform-features/always-watching.md +63 -0
- package/lib/templates/content/platform-features/instant-context.md +67 -0
- package/lib/templates/content/platform-features/instant-onboarding.md +80 -0
- package/lib/templates/content/platform-features/platform-overview.md +58 -0
- package/lib/templates/content/platform-features/proactive-alerts.md +88 -0
- package/lib/templates/content/platform-features/smart-escalation.md +93 -0
- package/lib/templates/content/product-features/ai-models.md +89 -0
- package/lib/templates/content/product-features/collaboration-tools.md +88 -0
- package/lib/templates/content/product-features/conversation-features.md +76 -0
- package/lib/templates/content/product-features/export-features.md +87 -0
- package/lib/templates/content/product-features/follow-up-questions.md +82 -0
- package/lib/templates/content/product-features/real-time-search.md +84 -0
- package/lib/templates/content/product-features/saved-searches.md +75 -0
- package/lib/templates/content/product-features/search-features.md +82 -0
- package/lib/templates/content/product-features/search-history.md +86 -0
- package/lib/templates/content/product-features/source-citations.md +100 -0
- package/lib/templates/content/scope-api/api-overview.md +104 -0
- package/lib/templates/content/search-modes/deep-research.md +109 -0
- package/lib/templates/content/search-modes/labs-features.md +81 -0
- package/lib/templates/content/search-modes/pro-search.md +75 -0
- package/lib/templates/content/search-modes/regular-search.md +86 -0
- package/lib/templates/content/security-compliance/audit-trail.md +112 -0
- package/lib/templates/content/security-compliance/compliance.md +120 -0
- package/lib/templates/content/security-compliance/data-encryption.md +94 -0
- package/lib/templates/content/security-compliance/security-overview.md +186 -0
- package/lib/templates/content/security-compliance/vm-isolation.md +126 -0
- package/lib/templates/content/solutions-engineering/bug-tracking-context.md +126 -0
- package/lib/templates/content/solutions-engineering/engineering-overview.md +107 -0
- package/lib/templates/content/solutions-engineering/error-monitoring.md +120 -0
- package/lib/templates/content/solutions-engineering/institutional-memory.md +120 -0
- package/lib/templates/content/solutions-marketing/brand-monitoring.md +135 -0
- package/lib/templates/content/solutions-marketing/content-automation.md +111 -0
- package/lib/templates/content/solutions-marketing/marketing-overview.md +108 -0
- package/lib/templates/content/solutions-marketing/social-media-management.md +108 -0
- package/lib/templates/content/solutions-sales/call-preparation.md +106 -0
- package/lib/templates/content/solutions-sales/crm-automation.md +119 -0
- package/lib/templates/content/solutions-sales/lead-management.md +108 -0
- package/lib/templates/content/solutions-sales/sales-overview.md +120 -0
- package/lib/templates/content/spaces-library/spaces-overview.md +89 -0
- package/lib/templates/content/student-hub/academic-research.md +106 -0
- package/lib/templates/content/student-hub/student-discounts.md +78 -0
- package/lib/templates/content/student-hub/student-overview.md +86 -0
- package/lib/templates/content/student-hub/study-tools.md +121 -0
- package/lib/templates/content/subscription-billing/billing-cycle.md +71 -0
- package/lib/templates/content/subscription-billing/billing-overview.md +72 -0
- package/lib/templates/content/subscription-billing/billing-support.md +74 -0
- package/lib/templates/content/subscription-billing/currency-support.md +57 -0
- package/lib/templates/content/subscription-billing/enterprise-pricing.md +74 -0
- package/lib/templates/content/subscription-billing/invoice-management.md +86 -0
- package/lib/templates/content/subscription-billing/payment-methods.md +77 -0
- package/lib/templates/content/subscription-billing/promotional-offers.md +81 -0
- package/lib/templates/content/subscription-billing/refund-policy.md +80 -0
- package/lib/templates/content/subscription-billing/student-discounts.md +88 -0
- package/lib/templates/content/subscription-billing/tax-information.md +86 -0
- package/lib/templates/content/technical-questions/ai-models-technical.md +87 -0
- package/lib/templates/content/technical-questions/api-technical.md +158 -0
- package/lib/templates/content/technical-questions/data-processing.md +102 -0
- package/lib/templates/content/technical-questions/database-architecture.md +120 -0
- package/lib/templates/content/technical-questions/infrastructure.md +132 -0
- package/lib/templates/content/technical-questions/performance-optimization.md +105 -0
- package/lib/templates/content/technical-questions/search-algorithms.md +105 -0
- package/lib/templates/content/technical-questions/technical-overview.md +107 -0
- package/lib/templates/content/threads/conversation-management.md +103 -0
- package/lib/templates/content/threads/threads-overview.md +92 -0
- package/lib/templates/content/troubleshooting/common-issues.md +115 -0
- package/lib/templates/content/use-cases/engineering-use-cases.md +123 -0
- package/lib/templates/content/use-cases/marketing-use-cases.md +128 -0
- package/lib/templates/content/use-cases/sales-use-cases.md +123 -0
- package/lib/templates/content/use-cases/support-use-cases.md +120 -0
- package/lib/templates/content/use-cases/use-cases-overview.md +115 -0
- package/lib/templates/content/what-is-yantra/getting-started-yantra.md +85 -0
- package/lib/{content → templates/content}/what-is-yantra/how-yantra-works.md +1 -1
- package/lib/{content → templates/content}/what-is-yantra/practical-tips-yantra.md +2 -1
- package/lib/{content → templates/content}/what-is-yantra/what-is-yantra-intro.md +1 -1
- package/lib/{content → templates/content}/what-is-yantra/yantra-discord-community.md +4 -1
- package/lib/{content → templates/content}/yantra-assistant/android-app.md +10 -0
- package/lib/{content → templates/content}/yantra-assistant/ios-app.md +10 -0
- package/lib/{content → templates/content}/yantra-assistant/mobile-app-overview.md +8 -0
- package/lib/{content → templates/content}/yantra-assistant/voice-assistant.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/admin-dashboard.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/custom-branding.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/dedicated-support.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/enterprise-overview.md +8 -0
- package/lib/{content → templates/content}/yantra-enterprise/sso-integration.md +10 -0
- package/lib/{content → templates/content}/yantra-enterprise/user-management.md +10 -0
- package/lib/{content → templates/content}/yantra-pro-max/billing-management.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/cancellation-refund.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/pro-pricing.md +13 -9
- package/lib/{content → templates/content}/yantra-pro-max/subscription-benefits.md +8 -0
- package/lib/{content → templates/content}/yantra-pro-max/upgrade-process.md +13 -0
- package/lib/{content → templates/content}/yantra-pro-max/yantra-max-features.md +8 -8
- package/lib/{content → templates/content}/yantra-pro-max/yantra-pro-overview.md +8 -8
- package/lib/utils/docsNavigation.d.ts +10 -0
- package/lib/utils/docsNavigation.d.ts.map +1 -0
- package/lib/utils/docsNavigation.js +209 -0
- package/lib/utils/docsNavigation.js.map +1 -0
- package/lib/utils/helpCenterUtils.d.ts.map +1 -1
- package/lib/utils/markdownLoader.d.ts +12 -4
- package/lib/utils/markdownLoader.d.ts.map +1 -1
- package/lib/utils/markdownLoader.js +362 -1163
- package/lib/utils/markdownLoader.js.map +1 -1
- package/package.json +23 -6
- package/lib/content/account-management/account-setup.md +0 -74
- package/lib/content/account-management/delete-account.md +0 -74
- package/lib/content/account-management/preferences.md +0 -73
- package/lib/content/account-management/privacy-settings.md +0 -73
- package/lib/content/account-management/profile-settings.md +0 -59
- package/lib/content/data-privacy/data-collection.md +0 -65
- package/lib/content/data-privacy/privacy-policy.md +0 -73
- package/lib/content/data-subject-privacy/data-access.md +0 -88
- package/lib/content/data-subject-privacy/data-portability.md +0 -108
- package/lib/content/data-subject-privacy/privacy-requests.md +0 -80
- package/lib/content/file-uploads/file-upload-overview.md +0 -65
- package/lib/content/getting-started/getting-started-guide.md +0 -65
- package/lib/content/product-features/ai-models.md +0 -84
- package/lib/content/product-features/collaboration-tools.md +0 -59
- package/lib/content/product-features/conversation-features.md +0 -45
- package/lib/content/product-features/export-features.md +0 -59
- package/lib/content/product-features/follow-up-questions.md +0 -59
- package/lib/content/product-features/real-time-search.md +0 -59
- package/lib/content/product-features/saved-searches.md +0 -59
- package/lib/content/product-features/search-features.md +0 -64
- package/lib/content/product-features/search-history.md +0 -59
- package/lib/content/product-features/source-citations.md +0 -59
- package/lib/content/scope-api/api-overview.md +0 -59
- package/lib/content/search-modes/deep-research.md +0 -60
- package/lib/content/search-modes/labs-features.md +0 -73
- package/lib/content/search-modes/pro-search.md +0 -59
- package/lib/content/search-modes/regular-search.md +0 -60
- package/lib/content/spaces-library/spaces-overview.md +0 -60
- package/lib/content/student-hub/academic-research.md +0 -61
- package/lib/content/student-hub/student-discounts.md +0 -74
- package/lib/content/student-hub/student-overview.md +0 -59
- package/lib/content/student-hub/study-tools.md +0 -59
- package/lib/content/subscription-billing/billing-cycle.md +0 -61
- package/lib/content/subscription-billing/billing-overview.md +0 -45
- package/lib/content/subscription-billing/billing-support.md +0 -59
- package/lib/content/subscription-billing/currency-support.md +0 -73
- package/lib/content/subscription-billing/enterprise-pricing.md +0 -60
- package/lib/content/subscription-billing/invoice-management.md +0 -59
- package/lib/content/subscription-billing/payment-methods.md +0 -67
- package/lib/content/subscription-billing/promotional-offers.md +0 -61
- package/lib/content/subscription-billing/refund-policy.md +0 -75
- package/lib/content/subscription-billing/student-discounts.md +0 -74
- package/lib/content/subscription-billing/tax-information.md +0 -59
- package/lib/content/technical-questions/ai-models-technical.md +0 -73
- package/lib/content/technical-questions/api-technical.md +0 -73
- package/lib/content/technical-questions/data-processing.md +0 -73
- package/lib/content/technical-questions/database-architecture.md +0 -73
- package/lib/content/technical-questions/infrastructure.md +0 -73
- package/lib/content/technical-questions/performance-optimization.md +0 -73
- package/lib/content/technical-questions/search-algorithms.md +0 -73
- package/lib/content/technical-questions/technical-overview.md +0 -73
- package/lib/content/threads/conversation-management.md +0 -59
- package/lib/content/threads/threads-overview.md +0 -60
- package/lib/content/troubleshooting/common-issues.md +0 -59
- package/lib/content/what-is-yantra/getting-started-yantra.md +0 -84
- package/lib/pages/ArticlePage/index.d.ts +0 -4
- package/lib/pages/ArticlePage/index.d.ts.map +0 -1
- package/lib/pages/ArticlePage/index.js +0 -190
- package/lib/pages/ArticlePage/index.js.map +0 -1
- package/lib/pages/HelpCenter/components/BookStack.js +0 -36
- package/lib/pages/HelpCenter/components/BookStack.js.map +0 -1
- package/lib/pages/LandingPage/components/Assets.js +0 -14
- package/lib/pages/LandingPage/components/Assets.js.map +0 -1
- package/lib/pages/LandingPage/components/Icons.d.ts +0 -14
- package/lib/pages/LandingPage/components/Icons.d.ts.map +0 -1
- package/lib/pages/LandingPage/components/Icons.js +0 -174
- package/lib/pages/LandingPage/components/Icons.js.map +0 -1
- package/lib/pages/LandingPage/components/SearchBar.d.ts +0 -8
- package/lib/pages/LandingPage/components/SearchBar.d.ts.map +0 -1
- package/lib/pages/LandingPage/components/SearchBar.js +0 -58
- package/lib/pages/LandingPage/components/SearchBar.js.map +0 -1
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
# Yantra Platform Overview
|
|
2
|
+
|
|
3
|
+
Yantra is an **AI-powered workforce platform** that deploys intelligent AI employees into your existing toolchain. Unlike traditional chatbots that wait for prompts, Yantra AI employees operate proactively — monitoring your communication channels, development pipelines, CRM systems, and project management tools around the clock.
|
|
4
|
+
|
|
5
|
+
## Why Yantra Exists
|
|
6
|
+
|
|
7
|
+
Modern teams lose significant productivity to repetitive operational tasks:
|
|
8
|
+
|
|
9
|
+
- **Context fragmentation**: Critical information is scattered across dozens of tools
|
|
10
|
+
- **Manual data entry**: Teams spend hours updating CRMs, logging notes, and syncing systems
|
|
11
|
+
- **Knowledge silos**: When team members leave or switch projects, institutional knowledge disappears
|
|
12
|
+
- **Alert overload**: Engineers, salespeople, and marketers drown in notifications without clear prioritization
|
|
13
|
+
|
|
14
|
+
Yantra solves these problems by providing AI employees that integrate directly into your workflow and handle operational overhead autonomously.
|
|
15
|
+
|
|
16
|
+
## Core Philosophy
|
|
17
|
+
|
|
18
|
+
### Proactive, Not Reactive
|
|
19
|
+
|
|
20
|
+
Traditional AI assistants answer when asked. Yantra AI employees **watch, learn, and act** without waiting for instructions. They surface issues before they escalate, update systems before data goes stale, and share context before you need to ask.
|
|
21
|
+
|
|
22
|
+
### Gradual Trust Model
|
|
23
|
+
|
|
24
|
+
Every Yantra AI employee starts in supervised mode. You review and approve all actions. Over time, as trust builds, you can grant more autonomy — letting the AI employee handle routine tasks independently while escalating only the important decisions.
|
|
25
|
+
|
|
26
|
+
### Built on OpenClaw
|
|
27
|
+
|
|
28
|
+
Yantra is built on top of [OpenClaw](https://github.com/openclaw), a battle-tested open-source AI agent framework. This means transparent, auditable AI behavior backed by a thriving community of contributors and enterprise users.
|
|
29
|
+
|
|
30
|
+
## What Yantra AI Employees Can Do
|
|
31
|
+
|
|
32
|
+
| Capability | Description |
|
|
33
|
+
| ------------------------------- | ---------------------------------------------------------- |
|
|
34
|
+
| **Continuous Monitoring** | Watch Slack, GitHub, error trackers, CRMs, and email 24/7 |
|
|
35
|
+
| **Contextual Correlation** | Connect data points across tools to surface insights |
|
|
36
|
+
| **Automated Actions** | Update CRMs, create tickets, draft messages, and log notes |
|
|
37
|
+
| **Intelligent Alerting** | Filter noise and escalate only what matters |
|
|
38
|
+
| **Institutional Memory** | Capture and recall every interaction, decision, and fix |
|
|
39
|
+
| **Multi-Channel Communication** | Interact via Slack, WhatsApp, Telegram, or email |
|
|
40
|
+
|
|
41
|
+
## Who Uses Yantra
|
|
42
|
+
|
|
43
|
+
- **Engineering Teams**: Monitor errors, correlate bugs with deployments, maintain institutional knowledge
|
|
44
|
+
- **Sales Teams**: Auto-update CRMs, prepare call briefs, ensure 100% follow-up on leads
|
|
45
|
+
- **Marketing Teams**: Manage social media presence, draft content from product updates, track brand mentions
|
|
46
|
+
- **Support Teams**: Route issues proactively, surface relevant context for customer problems
|
|
47
|
+
- **Operations Teams**: Keep systems synchronized and teams informed
|
|
48
|
+
|
|
49
|
+
## Getting Started
|
|
50
|
+
|
|
51
|
+
Setting up Yantra takes approximately 5 minutes:
|
|
52
|
+
|
|
53
|
+
1. **Connect your tools** — One-click OAuth for Slack, GitHub, HubSpot, Sentry, Linear, Gmail, and 40+ more
|
|
54
|
+
2. **Configure preferences** — Define what your AI employee should watch for and how to prioritize
|
|
55
|
+
3. **Start supervised** — Review and approve all AI actions to build trust
|
|
56
|
+
4. **Expand autonomy** — Gradually let your AI employee work independently on routine tasks
|
|
57
|
+
|
|
58
|
+
For detailed setup instructions, see the [Getting Started Guide](/help-center/ai-employees/getting-started-ai-employees).
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# Proactive Alerts — Know Before It Escalates
|
|
2
|
+
|
|
3
|
+
Yantra AI employees don't wait for you to discover problems — they detect issues early and notify you with full context, so you can respond before situations escalate.
|
|
4
|
+
|
|
5
|
+
## How Proactive Alerts Work
|
|
6
|
+
|
|
7
|
+
Your AI employee continuously analyzes events across all connected tools, looking for patterns and anomalies that indicate something needs attention. When it detects an issue, it:
|
|
8
|
+
|
|
9
|
+
1. **Correlates the signal** with data from other tools to understand the full scope
|
|
10
|
+
2. **Checks for existing responses** — whether someone is already handling it or a ticket exists
|
|
11
|
+
3. **Assesses severity** based on your configured thresholds and historical patterns
|
|
12
|
+
4. **Delivers a contextualized alert** with all relevant information and suggested actions
|
|
13
|
+
|
|
14
|
+
## Alert Types
|
|
15
|
+
|
|
16
|
+
### Error Spike Alerts
|
|
17
|
+
|
|
18
|
+
When your error monitoring tool (Sentry, Datadog, etc.) shows an unusual increase in exceptions, your AI employee investigates:
|
|
19
|
+
|
|
20
|
+
- Identifies the root error and affected components
|
|
21
|
+
- Checks if the spike correlates with a recent deployment
|
|
22
|
+
- Looks for existing tickets or ongoing fixes
|
|
23
|
+
- Notifies the appropriate team with a complete summary
|
|
24
|
+
|
|
25
|
+
### Customer Impact Alerts
|
|
26
|
+
|
|
27
|
+
When multiple customers report similar issues or a high-value account encounters a problem:
|
|
28
|
+
|
|
29
|
+
- Cross-references support channels with technical monitoring
|
|
30
|
+
- Surfaces the customer's history and account importance
|
|
31
|
+
- Suggests response templates based on similar past incidents
|
|
32
|
+
|
|
33
|
+
### Stale Activity Alerts
|
|
34
|
+
|
|
35
|
+
When important items stop progressing:
|
|
36
|
+
|
|
37
|
+
- Deals that haven't been updated in your CRM
|
|
38
|
+
- Pull requests awaiting review beyond your team's SLA
|
|
39
|
+
- Support tickets approaching response time limits
|
|
40
|
+
|
|
41
|
+
### Anomaly Alerts
|
|
42
|
+
|
|
43
|
+
When metrics deviate from normal patterns:
|
|
44
|
+
|
|
45
|
+
- Unusual traffic patterns or usage drops
|
|
46
|
+
- Unexpected changes in deployment frequency
|
|
47
|
+
- Communication volume spikes in specific channels
|
|
48
|
+
|
|
49
|
+
## Smart Escalation
|
|
50
|
+
|
|
51
|
+
Not every alert deserves your attention. Yantra uses **smart escalation** to ensure you only get interrupted when it genuinely matters:
|
|
52
|
+
|
|
53
|
+
### Severity Classification
|
|
54
|
+
|
|
55
|
+
- **Informational**: Logged for reference, included in daily briefings
|
|
56
|
+
- **Low**: Batched and delivered at your preferred check-in times
|
|
57
|
+
- **Medium**: Delivered promptly but not urgently
|
|
58
|
+
- **High**: Immediate notification through your preferred channel
|
|
59
|
+
- **Critical**: Multi-channel notification with escalation chain
|
|
60
|
+
|
|
61
|
+
### Escalation Rules
|
|
62
|
+
|
|
63
|
+
You define what constitutes each severity level:
|
|
64
|
+
|
|
65
|
+
- Error count thresholds (e.g., 50+ occurrences in 1 hour = Critical)
|
|
66
|
+
- Customer tier triggers (e.g., Enterprise account issues always escalate)
|
|
67
|
+
- Time-based rules (e.g., P0 tickets unresponded after 15 minutes)
|
|
68
|
+
- Custom keyword triggers (e.g., "data loss", "security breach")
|
|
69
|
+
|
|
70
|
+
## Configuring Alerts
|
|
71
|
+
|
|
72
|
+
Navigate to your AI employee's preferences to set:
|
|
73
|
+
|
|
74
|
+
- **Notification channels**: Where alerts get delivered (Slack, email, WhatsApp, Telegram)
|
|
75
|
+
- **Quiet hours**: When to batch non-critical alerts
|
|
76
|
+
- **Escalation chains**: Who gets notified if the primary responder doesn't acknowledge
|
|
77
|
+
- **Alert suppression**: Rules to prevent duplicate or noise alerts
|
|
78
|
+
|
|
79
|
+
## Alert History
|
|
80
|
+
|
|
81
|
+
All alerts are logged with:
|
|
82
|
+
|
|
83
|
+
- Timestamp and severity
|
|
84
|
+
- Full context at the time of alerting
|
|
85
|
+
- Actions taken (by the AI employee or team members)
|
|
86
|
+
- Resolution status and timeline
|
|
87
|
+
|
|
88
|
+
This history helps refine alert thresholds over time and provides data for post-incident reviews.
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# Smart Escalation — Only Get Pinged When It Matters
|
|
2
|
+
|
|
3
|
+
Yantra's smart escalation system ensures you're only interrupted for issues that truly require your attention, filtering out noise while never missing critical events.
|
|
4
|
+
|
|
5
|
+
## The Noise Problem
|
|
6
|
+
|
|
7
|
+
Modern development and business teams are overwhelmed by notifications:
|
|
8
|
+
|
|
9
|
+
- Hundreds of Slack messages daily
|
|
10
|
+
- Dozens of error alerts, most of which are duplicates or low priority
|
|
11
|
+
- CRM notifications for routine stage changes
|
|
12
|
+
- Email threads that don't require immediate action
|
|
13
|
+
|
|
14
|
+
This constant noise creates **alert fatigue**, causing teams to miss genuinely important issues buried in the flood. Yantra solves this by acting as an intelligent filter between your tools and your attention.
|
|
15
|
+
|
|
16
|
+
## How Smart Escalation Works
|
|
17
|
+
|
|
18
|
+
### 1. Signal Analysis
|
|
19
|
+
|
|
20
|
+
Every event from your connected tools is analyzed for:
|
|
21
|
+
|
|
22
|
+
- **Severity**: How impactful is this event?
|
|
23
|
+
- **Novelty**: Is this a new issue or a known one being tracked?
|
|
24
|
+
- **Scope**: How many users, customers, or systems are affected?
|
|
25
|
+
- **Trend**: Is this getting better or worse?
|
|
26
|
+
|
|
27
|
+
### 2. Context Enrichment
|
|
28
|
+
|
|
29
|
+
Before escalating, your AI employee gathers full context:
|
|
30
|
+
|
|
31
|
+
- Related events from other tools
|
|
32
|
+
- Historical data on similar issues
|
|
33
|
+
- Current status of any existing responses
|
|
34
|
+
- Who is available and responsible for this type of issue
|
|
35
|
+
|
|
36
|
+
### 3. Decision Logic
|
|
37
|
+
|
|
38
|
+
Based on your configured rules and the enriched context, Yantra decides:
|
|
39
|
+
|
|
40
|
+
- **Absorb silently**: Log it, include in daily summary
|
|
41
|
+
- **Batch for later**: Group with related items for periodic review
|
|
42
|
+
- **Notify gently**: Send a non-urgent message at your next check-in
|
|
43
|
+
- **Escalate immediately**: Push a notification through your preferred urgent channel
|
|
44
|
+
- **Trigger escalation chain**: If no response within the defined window, escalate to the next person
|
|
45
|
+
|
|
46
|
+
## Escalation Configuration
|
|
47
|
+
|
|
48
|
+
### Threshold-Based Rules
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
Error Count Rules:
|
|
52
|
+
- Less than 5 occurrences → Log only
|
|
53
|
+
- 5-25 occurrences → Batch notification
|
|
54
|
+
- 25-100 occurrences → Immediate notification
|
|
55
|
+
- 100+ occurrences → Critical escalation chain
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
### Customer Tier Rules
|
|
59
|
+
|
|
60
|
+
- **Enterprise accounts**: All issues escalated immediately
|
|
61
|
+
- **Pro accounts**: P0/P1 issues escalated, others batched
|
|
62
|
+
- **Free accounts**: Included in daily summaries
|
|
63
|
+
|
|
64
|
+
### Time-Based Rules
|
|
65
|
+
|
|
66
|
+
- **Business hours**: Standard escalation flow
|
|
67
|
+
- **Off hours**: Only critical issues escalate; everything else queued for morning
|
|
68
|
+
- **Weekends**: Emergency-only escalation with higher thresholds
|
|
69
|
+
|
|
70
|
+
## Escalation Chains
|
|
71
|
+
|
|
72
|
+
Define cascading notification paths for critical issues:
|
|
73
|
+
|
|
74
|
+
1. **Primary responder**: Notified first via Slack and email
|
|
75
|
+
2. **Backup responder**: Notified after 10 minutes if no acknowledgment
|
|
76
|
+
3. **Team lead**: Notified after 20 minutes if still unacknowledged
|
|
77
|
+
4. **On-call manager**: Final escalation for sustained non-response
|
|
78
|
+
|
|
79
|
+
## Feedback Loop
|
|
80
|
+
|
|
81
|
+
Yantra learns from your responses to refine escalation over time:
|
|
82
|
+
|
|
83
|
+
- If you consistently dismiss certain alert types, it adjusts thresholds
|
|
84
|
+
- If you escalate items that were batched, it increases their priority
|
|
85
|
+
- Monthly escalation reports help you tune your rules
|
|
86
|
+
|
|
87
|
+
## Getting Started
|
|
88
|
+
|
|
89
|
+
1. Connect your tools via [Integrations](/help-center/integrations/integrations-overview)
|
|
90
|
+
2. Set your default escalation preferences in the AI employee configuration
|
|
91
|
+
3. Define customer tiers and priority thresholds
|
|
92
|
+
4. Specify quiet hours and escalation chains
|
|
93
|
+
5. Review and refine based on the weekly escalation summary
|
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
# AI Models
|
|
2
|
+
|
|
3
|
+
Yantra integrates with multiple state-of-the-art AI models, automatically selecting the best one for each query to maximize quality, speed, and cost-efficiency.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Available Models
|
|
8
|
+
|
|
9
|
+
### Large language models
|
|
10
|
+
|
|
11
|
+
| Model | Provider | Best for | Speed |
|
|
12
|
+
| ----------------- | ------------------ | ----------------------------------------------------- | --------- |
|
|
13
|
+
| GPT-4o | OpenAI | Complex reasoning, nuanced analysis, multi-step tasks | Medium |
|
|
14
|
+
| GPT-4o mini | OpenAI | Quick factual lookups, simple Q&A | Fast |
|
|
15
|
+
| Claude 3.5 Sonnet | Anthropic | Long-form writing, careful instruction following | Medium |
|
|
16
|
+
| Claude 3 Haiku | Anthropic | Rapid responses, lightweight tasks | Very fast |
|
|
17
|
+
| Llama 3 70B | Meta (self-hosted) | On-premise deployments, privacy-sensitive workflows | Medium |
|
|
18
|
+
|
|
19
|
+
### Embedding models
|
|
20
|
+
|
|
21
|
+
| Model | Provider | Use case |
|
|
22
|
+
| ---------------------- | -------- | ------------------------------------ |
|
|
23
|
+
| text-embedding-3-large | OpenAI | Semantic search, document similarity |
|
|
24
|
+
| Cohere Embed v3 | Cohere | Multilingual content retrieval |
|
|
25
|
+
|
|
26
|
+
### Specialized models
|
|
27
|
+
|
|
28
|
+
- **Code models** — Optimized for programming questions, code generation, and debugging. Built on fine-tuned versions of GPT-4o and Claude.
|
|
29
|
+
- **Classification models** — Custom fine-tuned BERT variants for intent detection, content tagging, and routing.
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## Automatic Model Selection
|
|
34
|
+
|
|
35
|
+
By default, Yantra's **Intelligent Router** selects the best model for each query. You don't need to choose manually.
|
|
36
|
+
|
|
37
|
+
### How routing works
|
|
38
|
+
|
|
39
|
+
1. **Analyze the query** — The router classifies the intent (search, generate, summarize, analyze).
|
|
40
|
+
2. **Assess complexity** — Simple factual queries route to fast models; complex reasoning tasks route to frontier models.
|
|
41
|
+
3. **Check latency budget** — Real-time interactions prioritize speed; background tasks prioritize quality.
|
|
42
|
+
4. **Apply fallbacks** — If the primary model is unavailable or rate-limited, the router transparently falls back to an alternate provider.
|
|
43
|
+
|
|
44
|
+
> **Result:** You always get the best balance of quality and speed without managing model selection yourself.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## Manual Model Selection
|
|
49
|
+
|
|
50
|
+
Pro and Enterprise users can override automatic selection:
|
|
51
|
+
|
|
52
|
+
1. Click the **model selector** icon next to the search bar.
|
|
53
|
+
2. Choose your preferred model from the dropdown.
|
|
54
|
+
3. Your selection persists for the current session, or you can set a default under **Settings > Preferences > AI Model**.
|
|
55
|
+
|
|
56
|
+
### When to override
|
|
57
|
+
|
|
58
|
+
- **Consistency** — Use the same model for a series of related queries to get consistent output style.
|
|
59
|
+
- **Experimentation** — Compare responses from different models side-by-side.
|
|
60
|
+
- **Compliance** — Select on-premise models (Llama 3) when data cannot leave your infrastructure.
|
|
61
|
+
|
|
62
|
+
---
|
|
63
|
+
|
|
64
|
+
## Model Capabilities
|
|
65
|
+
|
|
66
|
+
### What every model can do
|
|
67
|
+
|
|
68
|
+
- Generate natural language responses in 50+ languages
|
|
69
|
+
- Cite sources with inline references
|
|
70
|
+
- Format output as prose, lists, tables, or code blocks
|
|
71
|
+
- Maintain multi-turn conversation context
|
|
72
|
+
- Respect custom system prompts and guardrails
|
|
73
|
+
|
|
74
|
+
### Advanced capabilities (frontier models only)
|
|
75
|
+
|
|
76
|
+
- Multi-step reasoning with chain-of-thought
|
|
77
|
+
- Image and document analysis (GPT-4o)
|
|
78
|
+
- 100K+ token context windows for long documents
|
|
79
|
+
- Function calling and structured JSON output
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## Model Updates
|
|
84
|
+
|
|
85
|
+
Yantra regularly updates to the latest model versions:
|
|
86
|
+
|
|
87
|
+
- **Automatic upgrades** — When providers release improved versions, Yantra transitions within 2 weeks after internal quality validation.
|
|
88
|
+
- **Version pinning** — Enterprise customers can pin specific model versions for stability.
|
|
89
|
+
- **Changelog** — All model changes are documented in the [Product Changelog](https://yantra.ai/changelog).
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# Collaboration Tools
|
|
2
|
+
|
|
3
|
+
Work together with your team using shared searches, workspaces, and real-time collaboration features.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Shared Workspaces
|
|
8
|
+
|
|
9
|
+
Every team on Yantra gets a shared workspace where members can collaborate:
|
|
10
|
+
|
|
11
|
+
### What you can share
|
|
12
|
+
|
|
13
|
+
| Content type | How to share | Permissions |
|
|
14
|
+
| -------------------- | ------------------------------------- | ------------ |
|
|
15
|
+
| Search results | Click **Share** on any result card | View or Edit |
|
|
16
|
+
| Conversations | Share a thread link with team members | View only |
|
|
17
|
+
| Saved searches | Add to a shared collection | View or Edit |
|
|
18
|
+
| AI employee insights | Post to a shared channel | View only |
|
|
19
|
+
|
|
20
|
+
### Setting up a workspace
|
|
21
|
+
|
|
22
|
+
1. Go to **Settings > Team > Create Workspace**.
|
|
23
|
+
2. Name your workspace and add a description.
|
|
24
|
+
3. Invite members via email or shareable link.
|
|
25
|
+
4. Set default permissions (Viewer, Editor, or Admin).
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## Sharing Searches
|
|
30
|
+
|
|
31
|
+
### Share a single result
|
|
32
|
+
|
|
33
|
+
1. Find the result you want to share.
|
|
34
|
+
2. Click the **Share** icon (arrow) on the result card.
|
|
35
|
+
3. Choose how to share:
|
|
36
|
+
- **Copy link** — Anyone with the link (and workspace access) can view.
|
|
37
|
+
- **Send to teammate** — Select a team member to notify directly.
|
|
38
|
+
- **Post to Slack** — Share directly to a connected Slack channel.
|
|
39
|
+
|
|
40
|
+
### Share an entire search
|
|
41
|
+
|
|
42
|
+
Click **Share Search** at the top of the results page to share the query and all results as a snapshot.
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## Real-Time Collaboration
|
|
47
|
+
|
|
48
|
+
### Live cursors
|
|
49
|
+
|
|
50
|
+
When multiple team members view the same workspace, you'll see their cursors and selections in real time — no more "are you looking at this?" messages.
|
|
51
|
+
|
|
52
|
+
### Comments and annotations
|
|
53
|
+
|
|
54
|
+
- **Inline comments** — Click any result or AI response to add a comment. Team members are notified.
|
|
55
|
+
- **Annotations** — Highlight text and add notes for context. Annotations are visible to all workspace members.
|
|
56
|
+
- **@mentions** — Tag teammates in comments to draw their attention.
|
|
57
|
+
|
|
58
|
+
### Activity feed
|
|
59
|
+
|
|
60
|
+
The workspace activity feed shows:
|
|
61
|
+
|
|
62
|
+
- Who shared or saved what
|
|
63
|
+
- Comments and annotations
|
|
64
|
+
- AI employee actions and recommendations
|
|
65
|
+
- Integration updates
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## Team Permissions
|
|
70
|
+
|
|
71
|
+
| Role | Can view | Can edit | Can share externally | Can manage members |
|
|
72
|
+
| ------ | -------- | -------- | -------------------- | ------------------ |
|
|
73
|
+
| Viewer | Yes | No | No | No |
|
|
74
|
+
| Editor | Yes | Yes | No | No |
|
|
75
|
+
| Admin | Yes | Yes | Yes | Yes |
|
|
76
|
+
| Owner | Yes | Yes | Yes | Yes |
|
|
77
|
+
|
|
78
|
+
Permissions can be set at the workspace level or per-item.
|
|
79
|
+
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
## Integration with Chat Tools
|
|
83
|
+
|
|
84
|
+
Collaboration extends beyond the Yantra app:
|
|
85
|
+
|
|
86
|
+
- **Slack** — Share results, receive team updates, and interact with your AI employee directly in Slack channels.
|
|
87
|
+
- **Microsoft Teams** — Same capabilities as Slack for Teams-first organizations.
|
|
88
|
+
- **Email** — Share results and summaries via email with one click.
|
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
# Conversation Features
|
|
2
|
+
|
|
3
|
+
Yantra doesn't just return search results — it lets you have a natural back-and-forth conversation to refine your understanding and go deeper on any topic.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## How Conversations Work
|
|
8
|
+
|
|
9
|
+
Every search on Yantra can become a conversation. After receiving an initial response, you can:
|
|
10
|
+
|
|
11
|
+
- **Ask follow-up questions** — Yantra remembers the full context of your conversation, so you don't need to repeat yourself.
|
|
12
|
+
- **Refine your query** — If the first response isn't quite right, clarify what you meant or ask for a different angle.
|
|
13
|
+
- **Go deeper** — Request more detail on a specific part of the response.
|
|
14
|
+
- **Switch direction** — Ask about a related topic — Yantra understands the connection.
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## Context Retention
|
|
19
|
+
|
|
20
|
+
### What Yantra remembers
|
|
21
|
+
|
|
22
|
+
Within a conversation thread, Yantra maintains:
|
|
23
|
+
|
|
24
|
+
| Context type | Example |
|
|
25
|
+
| --------------------- | --------------------------------------------------------------- |
|
|
26
|
+
| Previous questions | Your full query history in the thread |
|
|
27
|
+
| Entities mentioned | People, products, companies, dates you've referenced |
|
|
28
|
+
| Preferences expressed | "Show me only academic sources" applies to subsequent responses |
|
|
29
|
+
| Response references | "Expand on point #3" refers to the current response |
|
|
30
|
+
|
|
31
|
+
### Context window
|
|
32
|
+
|
|
33
|
+
- **Standard mode** — Retains the last 10 exchanges (~50,000 tokens of context).
|
|
34
|
+
- **Pro Search** — Extended context with up to 100,000 tokens.
|
|
35
|
+
- **Deep Research** — Full conversation history for the research session.
|
|
36
|
+
|
|
37
|
+
> **Tip:** If a conversation gets very long, start a new thread for a fresh topic. You can always reference previous threads.
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## Conversation Actions
|
|
42
|
+
|
|
43
|
+
### During a conversation
|
|
44
|
+
|
|
45
|
+
| Action | How | Description |
|
|
46
|
+
| ------------------- | ----------------------------------- | ---------------------------------------------------- |
|
|
47
|
+
| Copy response | Click the copy icon | Copies the formatted response to your clipboard |
|
|
48
|
+
| Share response | Click the share icon | Share a specific response with your team |
|
|
49
|
+
| Edit your message | Click the edit icon on your message | Rephrase your question to get a different response |
|
|
50
|
+
| Branch conversation | Click "Branch" | Create a parallel thread exploring a different angle |
|
|
51
|
+
| Rate response | Thumbs up/down | Help improve response quality over time |
|
|
52
|
+
|
|
53
|
+
### After a conversation
|
|
54
|
+
|
|
55
|
+
- **Save to collection** — Add the entire conversation to a saved collection for future reference.
|
|
56
|
+
- **Export** — Download the conversation as Markdown, PDF, or plain text.
|
|
57
|
+
- **Continue later** — All conversations are saved automatically. Pick up where you left off from the Threads page.
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## Multi-Language Support
|
|
62
|
+
|
|
63
|
+
Conversations work in 50+ languages:
|
|
64
|
+
|
|
65
|
+
- **Auto-detect** — Yantra automatically responds in the language you use.
|
|
66
|
+
- **Switch mid-conversation** — You can change languages at any point. Yantra adapts.
|
|
67
|
+
- **Translate** — Ask Yantra to translate a response into a different language.
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
## Best Practices
|
|
72
|
+
|
|
73
|
+
1. **Be specific** — Instead of "tell me more," ask "what are the cost implications of option B?"
|
|
74
|
+
2. **Use context** — Reference earlier parts of the conversation: "Going back to the security concern you mentioned…"
|
|
75
|
+
3. **One topic per thread** — Keep conversations focused for better AI context management.
|
|
76
|
+
4. **Rate responses** — Thumbs up/down helps Yantra learn your preferences over time.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
# Export Features
|
|
2
|
+
|
|
3
|
+
Take your research anywhere. Yantra lets you export search results, conversations, and reports in multiple formats for offline use, sharing, or integration with other tools.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Supported Export Formats
|
|
8
|
+
|
|
9
|
+
| Format | Best for | Includes |
|
|
10
|
+
| -------------- | ---------------------------------------- | ----------------------------------------------- |
|
|
11
|
+
| **Markdown** | Documentation, GitHub, Notion | Formatted text with headers, lists, code blocks |
|
|
12
|
+
| **PDF** | Formal reports, presentations, archiving | Styled document with Yantra branding (optional) |
|
|
13
|
+
| **Plain text** | Simple sharing, email | Clean text without formatting |
|
|
14
|
+
| **JSON** | API integrations, data processing | Structured data with metadata |
|
|
15
|
+
| **CSV** | Spreadsheets, data analysis | Tabular data (results, citations, metadata) |
|
|
16
|
+
| **HTML** | Web publishing, email newsletters | Rendered HTML with styling |
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
## What You Can Export
|
|
21
|
+
|
|
22
|
+
### Search results
|
|
23
|
+
|
|
24
|
+
Export individual results or entire result sets:
|
|
25
|
+
|
|
26
|
+
1. Open a search result page.
|
|
27
|
+
2. Click **Export** in the top-right toolbar.
|
|
28
|
+
3. Select results to include (all or specific ones).
|
|
29
|
+
4. Choose your format.
|
|
30
|
+
5. Click **Download** or **Copy to clipboard**.
|
|
31
|
+
|
|
32
|
+
### Conversations
|
|
33
|
+
|
|
34
|
+
Export complete conversation threads:
|
|
35
|
+
|
|
36
|
+
1. Open the conversation you want to export.
|
|
37
|
+
2. Click the **⋯** menu > **Export Conversation**.
|
|
38
|
+
3. Choose the range (entire thread or selected messages).
|
|
39
|
+
4. Select format and click **Export**.
|
|
40
|
+
|
|
41
|
+
### Collections
|
|
42
|
+
|
|
43
|
+
Export entire saved collections at once:
|
|
44
|
+
|
|
45
|
+
1. Open the collection from your **Library**.
|
|
46
|
+
2. Click **Export Collection**.
|
|
47
|
+
3. Choose format and options.
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
## Export Options
|
|
52
|
+
|
|
53
|
+
Customize your exports:
|
|
54
|
+
|
|
55
|
+
| Option | Description | Available for |
|
|
56
|
+
| -------------------- | ------------------------------------- | ------------------- |
|
|
57
|
+
| Include sources | Add source URLs and citation metadata | All formats |
|
|
58
|
+
| Include timestamps | Add dates for each interaction | JSON, CSV, Markdown |
|
|
59
|
+
| Include images | Embed referenced images | PDF, HTML, Markdown |
|
|
60
|
+
| Custom header/footer | Add your own branding or notes | PDF only |
|
|
61
|
+
| Strip formatting | Export raw content without styling | All formats |
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## Bulk Export
|
|
66
|
+
|
|
67
|
+
For large-scale exports (data backup, compliance, migration):
|
|
68
|
+
|
|
69
|
+
1. Go to **Settings > Privacy > Export Data**.
|
|
70
|
+
2. Select data categories: searches, conversations, collections, preferences, account data.
|
|
71
|
+
3. Click **Request Export**.
|
|
72
|
+
4. You'll receive a download link via email within 24 hours.
|
|
73
|
+
5. The archive includes JSON and CSV files organized by category.
|
|
74
|
+
|
|
75
|
+
> **Enterprise customers** can set up automated scheduled exports via the API.
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## API Export
|
|
80
|
+
|
|
81
|
+
Use the export API for programmatic access:
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
GET /v1/export/searches?format=json&from=2024-01-01&to=2024-12-31
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
The API supports all formats, date ranges, and filtering options available in the UI.
|
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
# Follow-Up Questions
|
|
2
|
+
|
|
3
|
+
Yantra intelligently suggests follow-up questions to help you explore topics more deeply without having to think of what to ask next.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## How Follow-Up Questions Work
|
|
8
|
+
|
|
9
|
+
After every response, Yantra analyzes the content and generates 2–4 suggested follow-up questions. These appear as clickable chips below the response.
|
|
10
|
+
|
|
11
|
+
### What drives the suggestions
|
|
12
|
+
|
|
13
|
+
| Factor | How it's used |
|
|
14
|
+
| --------------------- | ------------------------------------------------------------- |
|
|
15
|
+
| Response content | Identifies subtopics or details worth exploring |
|
|
16
|
+
| Common next questions | Based on what other users typically ask after similar queries |
|
|
17
|
+
| Your history | Considers your recent searches and interests |
|
|
18
|
+
| Conversation context | Adjusts suggestions based on the flow of the current thread |
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Types of Follow-Up Questions
|
|
23
|
+
|
|
24
|
+
### Deepening questions
|
|
25
|
+
|
|
26
|
+
Go further into a topic already covered:
|
|
27
|
+
|
|
28
|
+
- _"What are the specific performance benchmarks for this approach?"_
|
|
29
|
+
- _"Can you explain how the encryption layer works in more detail?"_
|
|
30
|
+
|
|
31
|
+
### Broadening questions
|
|
32
|
+
|
|
33
|
+
Explore related but different angles:
|
|
34
|
+
|
|
35
|
+
- _"How does this compare to the alternative approaches?"_
|
|
36
|
+
- _"What are the security implications of this architecture?"_
|
|
37
|
+
|
|
38
|
+
### Practical questions
|
|
39
|
+
|
|
40
|
+
Move from theory to application:
|
|
41
|
+
|
|
42
|
+
- _"How would I implement this in a Node.js application?"_
|
|
43
|
+
- _"What's the estimated cost for a team of 50 users?"_
|
|
44
|
+
|
|
45
|
+
### Clarifying questions
|
|
46
|
+
|
|
47
|
+
Get more precise information:
|
|
48
|
+
|
|
49
|
+
- _"Does this apply to the free tier or only paid plans?"_
|
|
50
|
+
- _"Is this feature available on mobile as well?"_
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
## Using Follow-Up Questions
|
|
55
|
+
|
|
56
|
+
### Click to ask
|
|
57
|
+
|
|
58
|
+
Simply click any suggested follow-up question to instantly submit it. The response will appear in the same conversation thread, maintaining full context.
|
|
59
|
+
|
|
60
|
+
### Edit before asking
|
|
61
|
+
|
|
62
|
+
Hover over a suggestion and click the **edit** icon to modify the question before submitting. This is useful when the suggestion is close but you want to be more specific.
|
|
63
|
+
|
|
64
|
+
### Ignore and ask your own
|
|
65
|
+
|
|
66
|
+
Follow-up suggestions are optional. You can always type your own question in the input field. Suggested questions won't interfere.
|
|
67
|
+
|
|
68
|
+
---
|
|
69
|
+
|
|
70
|
+
## Customization
|
|
71
|
+
|
|
72
|
+
### Toggle follow-up suggestions
|
|
73
|
+
|
|
74
|
+
If you prefer a cleaner interface, disable automatic suggestions:
|
|
75
|
+
|
|
76
|
+
**Settings > Preferences > AI Interaction > Auto follow-up questions** → Off
|
|
77
|
+
|
|
78
|
+
When disabled, you can still manually request suggestions by typing "Suggest follow-up questions" in the chat.
|
|
79
|
+
|
|
80
|
+
### Feedback loop
|
|
81
|
+
|
|
82
|
+
Click the **×** on any suggestion to dismiss it. Over time, Yantra learns which types of follow-ups are useful to you and adjusts accordingly.
|