forked from stackblitz-labs/bolt.diy
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add bar in input chat #5
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* cookie fix * fix: git private clone with custom proxy * list -fix
* commit * Create .env.example * Update docker-compose.yaml --------- Co-authored-by: Anirban Kar <[email protected]>
* Create docker.yaml * Add build target * Use build target var * Use github token instead
* Update docker.yaml * Fix indentation in docker workflow file
…model integration with AWS Bedrock (stackblitz-labs#974) * feat: Integrate AWS Bedrock with Claude 3.5 Sonnet, Claude 3 Sonnet, and Claude 3.5 Haiku * update Dockerfile for AWS Bedrock configuration * feat: add new Bedrock model 'Mistral' and update Haiku to version 3 * feat: add new bedrock model Nova Lite and Nova Pro * Update README documentation to reflect the latest changes * Add the icon for aws bedrock * add support for serialized AWS Bedrock configuration in api key
…itz-labs#1008) * fix: ollama and lm studio url issue fix for docker and build * vite config fix
* fix: streaming issue fixed for build versions * added keep-alive header
Added ⬜ Granite Integration
) * feat: enhance chat import with multi-format support - Add support for importing chats from different formats: - Standard Bolt format - Chrome extension format - History array format - Bolt export format - Add Import Chats button to Data Management - Add proper error handling and logging - Update README with backup/restore feature * refactor: simplify chat import formats - Remove multi-format support from DataTab - Keep only standard Bolt export formats - Simplify ImportButtons to handle standard format only
* fixed formatting of faq and enhanced styling * save * did further improvements and fixing the sidebar --------- Co-authored-by: Anirban Kar <[email protected]>
…anager component (stackblitz-labs#732) * fixed stackblitz-labs#333 * Added instruction in case api-key is not set. * addressed some of the review changes: 1. moved function definiton to useCallback. 2. added a cache to store the env key status and the api call is made only on a cache miss. * Manages the API-key entered via UI in a better way. - Persist API keys in cookies when entered via UI - Automatically load saved keys when switching between providers - Preserve existing functionality for environment variable based keys * Re-used map from utils/constants file. * Code cleanup - Removed redundant API key init in BaseChat as its already handled by APIKeyManager component.
chore: Update README.md with new model integration todo
Add Todo
…bs#1077) * fix: api-key manager cleanup and log error on llm call * log improved
…parency-about-development docs: document how we work
Co-authored-by: 刘一奇 <[email protected]>
* added the "Open Preview in a New Tab" * enhancement [Open Preview] [▼] // Two buttons side by side | +-- [Mobile (375x667)] // Dropdown menu |-- [Tablet (768x1024)] |-- [Laptop (1366x768)] +-- [Desktop (1920x1080)] * Update Preview.tsx * Update Preview.tsx
* Use backend API route to fetch dynamic models # Conflicts: # app/components/chat/BaseChat.tsx * Override ApiKeys if provided in frontend * Remove obsolete artifact * Transport api keys from client to server in header * Cache static provider information * Restore reading provider settings from cookie * Reload only a single provider on api key change * Transport apiKeys and providerSettings via cookies. While doing this, introduce a simple helper function for cookies
- Enhanced text for bolt.diy docs section and better visibility to guide people there instead using github readme which is more for devs - added NodeJS based applications, as this is not clear and some people asked about in the community
…patch-readme-changes-v1 docs: update README.md
docs: replace docker-compose with docker compose
…VIEW_V3 fix: for Open preview in a new tab.
- Created new TokenUsageBar component - Added token usage notification at the top of chat - Styled with dark theme and purple accent color - Added responsive width and rounded borders
- Fix token usage bar rendering and update logic - Update token usage store integration - Fix infinite loop issues with store selectors - Update max tokens to 10000 - Add better error handling for token annotations
- Remove merge conflict markers - Fix component structure and nesting - Keep TokenUsageBar implementation from add-bar-in-input-chat branch - Remove unused imports
- Fix ImportButtons component to properly use props - Add TooltipProvider wrapper in BaseChat - Clean up component hierarchy and fix nested structure - Fix type errors in component props
- Fix missing closing tags and JSX hierarchy - Clean up duplicate code blocks - Improve keyboard shortcut formatting - Add component display name - Fix line endings and whitespace - Remove unused ImportFolderButton reference
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.