In an announcement titled “AI Artifact User Storage,” sam introduces AI Artifact storage, building on December’s Web Artifacts feature, enabling dynamic, user-specific interactions like surveys and games via embedded artifacts. A demo artifact by Falco showcases user storage capabilities, with a link to its source. EricGT suggests appending “ask questions as needed” to prompts for better AI output. chrism asks for clarification on user storage, which sam clarifies is tied to user ID, not session. darkpixlz praises the feature but questions why artifact creation is AI-only, sparking support from MachineScholar and NateDhaliwal for manual artifact creation, especially for coding forums. sam acknowledges the request and suggests an admin API as an interim solution, leading MachineScholar to open a dedicated feature request topic. NateDhaliwal inquires how artifacts access usernames; sam explains via iframe messaging and shares the controller code. iamcapote notes potential synergy with Google’s A2U project. The discussion highlights enthusiasm for the feature and community-driven ideas for expanding its accessibility and utility.
While the AI will often ask several questions, I find that the questions are valid and in taking the time to answer them, it does make for a much better result. Even at the end of the answers to the questions again add ask questions as needed. This sometimes goes for a few rounds but in the end 5 minutes of added Q&A saves about 20 or minutes of multiple round trips.
זה די מגניב, בהתחלה התעלמתי מהנושא כי ראיתי “AI” בכותרת אבל זו בעצם תכונה נחמדה. עם זאת, למה זה נעול מאחורי AI בלבד? זה נראה שיכול להיות הרבה יותר חזק אם כל אחד יכול ליצור את החפצים האלה.
I second this! For example, having an interface where the code for artifacts and key/value pairs for storage can be manually inserted/updated would be neat.
Otherwise you’re forced to either use the web creator persona (can get expensive) or ssh tunnel into the database and manually edit the code in the relevant database row/column (can get risky)
אני לא מתנגד שיהיה מנגנון, אבל זהו חלק עבודה גדול למדי, יש הרבה ממשק משתמש, דבר ביניים שאני יכול לעשות כנראה הוא לספק API ניהולי ליצירת / עריכת ארטיפקטים וכן הלאה.
Artifacts use a messaging system from the sandboxed IFRAME back to the hosting page can communicate directly with the instance. That is how they can store/retrieve user data and get username/avatar template etc…