The committed README nested the hackathon tags under short_description, so
HF rejected the push ("short_description must be <= 60 characters"). Commit
the corrected working-tree README: tags under a proper `tags:` key, plus the
title / short_description / video / blog updates.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Auto-select ZeroGPU backend on the Space; register @spaces.GPU in app.py
The Space failed with "No @spaces.GPU function detected during startup"
because the zerogpu backend (and its decorated function) only imports when
MINIFAM_BACKEND=zerogpu, which wasn't taking effect (no model download in
the logs). Now the backend auto-selects: zerogpu when the `spaces` package
is present (i.e. on the Space), openai locally. Also bind the decorated
generate fn into app.py so ZeroGPU's startup scan reliably finds it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Update README.md to add a blank line for improved readability
ZeroGPU can't host a persistent Ollama/llama.cpp server, so run the model
in-process via transformers inside an @spaces.GPU function. A backend seam
(minifam/llm.py) dispatches on MINIFAM_BACKEND; the default "openai" path
(local Ollama) is unchanged.
- minifam/llm.py: backend dispatcher (openai | zerogpu)
- minifam/llm_zerogpu.py: in-process generate + <tool_call> parsing
- agent.py: backend-agnostic, dict-normalized tool loop
- requirements.txt: spaces/transformers/accelerate/bitsandbytes (Linux-marked)
- README.md: python_version 3.12 (ZeroGPU requirement)
- bootstrap.py: self-disable when MINIFAM_BACKEND=zerogpu
Set MINIFAM_BACKEND=zerogpu and MINIFAM_MODEL=Qwen/Qwen3-8B on the Space.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add Ollama server bootstrap functionality and update chat error handling
- Introduced a new `bootstrap.py` module to manage the setup of a local Ollama server in Hugging Face GPU Spaces, allowing for seamless integration without Docker.
- Updated the `app.py` file to call `bootstrap.ensure_ollama()` for server initialization and modified chat error handling to provide more informative messages during model warmup.
- Enhanced the README.md with instructions for running the model locally and using different backends, improving user guidance.
This commit enhances the application's capability to run a local model server efficiently while improving user experience during chat interactions.
Refactor notes functionality for shared family access
- Updated the notes API to remove member-specific access, allowing for a single shared family notebook.
- Modified frontend components to reflect the shared nature of notes, enhancing the user experience.
- Adjusted serialization and storage methods to support the new shared notes structure.
- Incremented asset versioning in index.html to ensure proper caching.
This commit improves the notes feature by centralizing access for all family members, fostering collaboration and ease of use.
Add calendar functionality and enhance UI components
- Introduced a family calendar feature, allowing users to add events and tasks, with options to assign members and set dates/times.
- Implemented API endpoints for calendar management, including adding, completing, and removing calendar items.
- Enhanced the frontend to display calendar items, including today's events and tasks, with a user-friendly interface.
- Updated CSS for calendar components to improve visual layout and usability.
- Incremented asset versioning in index.html to ensure proper caching.
This commit significantly enhances the application's functionality by integrating a shared family calendar, improving user experience and organization.
Update asset versioning and enhance UI components
- Incremented version numbers for assets in index.html to ensure proper caching.
- Improved button styling in minifam.css for better visual appeal and usability.
- Enhanced the Home component in screens1.jsx to display emojis alongside meal indicators, enriching the user interface.
- Updated meals display in screens3.jsx to include emojis for better representation of dishes.
This commit enhances the overall user experience by improving asset management and UI elements.
Update frontend components for chat functionality and asset versioning
- Incremented version numbers for assets in index.html to ensure proper caching.
- Introduced a ChatProvider in live.jsx to manage chat state and persist conversation across navigation.
- Refactored Chat component in screens1.jsx to utilize the new ChatProvider, enhancing the separation of concerns.
- Updated app.jsx to include ChatProvider, ensuring chat context is available throughout the application.
This commit enhances the chat experience by maintaining state across different screens and improving asset management.
Add emoji support for recipes and enhance storage functionality
- Introduced an emoji field in recipe markdown files to visually represent dishes, improving user engagement.
- Updated the recipe serialization process to include emoji, with a fallback mechanism for older recipes without specified emojis.
- Enhanced the add_recipe function to accept an emoji parameter, ensuring new recipes can be saved with a representative emoji.
- Modified the frontend components to display emojis alongside recipe titles, enriching the user interface.
This commit enhances the recipe management system by integrating emojis, making the application more visually appealing and user-friendly.
Update frontend files for live data synchronization and asset versioning
- Incremented version numbers for assets in index.html to ensure proper caching.
- Implemented a live refresh mechanism in live.jsx to automatically update data when files change, enhancing user experience without manual reloads.
- Refactored useLive hook to support live data fetching and synchronization with disk changes.
- Updated Notes component in screens3.jsx to utilize the new live refresh functionality for real-time note updates.
This commit improves the application's responsiveness to data changes, providing a seamless user experience.
Update frontend components and CSS for improved tag management
- Updated the index.html file to increment version numbers for assets.
- Refactored CSS to enhance the styling of tags, including adjustments to font size, weight, and background.
- Modified JSX files to replace the vegetarian flag with a flexible tag system, allowing for multiple dietary tags.
- Improved meal display logic to accommodate the new tagging system, enhancing user experience and clarity.
This commit enhances the frontend's ability to manage and display dietary preferences more effectively.
- Introduced a detailed meal planning prompt to guide users in creating diverse meal plans for lunch and dinner.
- Increased the maximum tool rounds from 6 to 12 to accommodate more complex meal planning scenarios.
- Updated the agent's system prompt to include the new meal planning guidelines, improving user experience and functionality.
This commit refines the meal planning feature, ensuring users can create varied and personalized meal plans effectively.
Update meal planning and frontend components in MiniFam
- Updated the meal planning system to support both lunch and dinner for each day, enhancing the user experience.
- Modified the frontend to reflect these changes, including updates to the meal display and CSS for better layout.
- Adjusted the agent's system prompt to clarify meal planning capabilities.
- Improved serialization and storage functions to accommodate the new meal structure.
This commit enhances the overall functionality and usability of the meal planning feature in the application.
Add family context for dietary preferences in MiniFam
- Introduced the `_family_context` function to generate a snapshot of family members and their food preferences.
- Updated the system prompt to include dietary considerations when planning meals.
- Enhanced the agent's response to ensure meal suggestions respect all family members' dietary needs.
This commit improves the agent's ability to provide personalized meal planning based on family dietary restrictions.
- Introduced the `set_food_preferences` function to update dietary preferences for family members.
- Updated the agent's onboarding instructions to include prompts for food preferences.
- Enhanced the tools to support setting food preferences and modified the frontend to reflect these changes.
- Updated the member data structure in JSON to include food preferences.
This commit enhances dietary management capabilities for family members in the application.
Refactor member management to include food preferences in MiniFam
- Updated the `add_member` function to accept and store food preferences instead of a vegetarian flag.
- Modified frontend components to handle food preferences input and display.
- Adjusted API responses and serialization to reflect changes in member data structure.
- Enhanced CSS for new input fields related to food preferences.
This commit improves the flexibility of dietary management for family members.
Add onboarding features for family member management in MiniFam
- Introduced new tools for adding and listing family members.
- Updated agent prompts to guide users during first-time setup.
- Enhanced frontend to handle onboarding state, including navigation restrictions and greeting messages.
- Adjusted API responses to support new member functionalities.
- Updated CSS for disabled navigation items.
This commit improves the user experience for new users setting up their family in the application.
Adjust gap in .brand class from 11px to 8px for improved layout consistency in minifam.css
Track logo.png with Git LFS so Hugging Face Xet accepts the push.
Co-authored-by: Cursor <cursoragent@cursor.com>
Refactor MiniFam to use gradio.Server for the main entry point, enhancing API endpoints for chat, recipes, notes, meal plans, and member management. Introduce a no-cache static file serving mechanism and update member data handling with JSON storage.
