OpenClaw text-message agents yield 12 ideas daily – 40-day UI rebuild

OpenClaw (Karpathy usage): A shared clip shows OpenClaw being used as a “text-message control plane” for a home—send a message, have agents discover devices (e.g., Sonos) on the local network, and then control systems like lights and HVAC, as described in the Podcast clip summary.

Video loads on view

The same post frames it as “no code” home automation and attributes the demo to a segment from No Priors, with the full context linked in the Podcast episode.

OpenClaw (Home ops risk): The same OpenClaw clip is circulated with an unusually strong capability claim—agents can “search the network + hack in” to connected hardware, then operate music, lights, HVAC, and security via texts, per the Capability framing.

Video loads on view

For creators, the immediate implication is operational: this isn’t just content automation; it’s an agent UI touching real devices and accounts, using discovery and control patterns that merit a different threat model than “generate a video.”

OpenClaw (Story development loop): A creator reports an OpenClaw agent that reads multiple sites daily as “fleeting” inspiration inputs (separate searches for movie/shorts/TV), then returns 12 story ideas and records each into Obsidian, as described in the Workflow description and reiterated in the Why it helps.

This is a clean example of “creative admin” automation: sourcing prompts from the world, turning them into pitchable kernels, and filing them into a system of record without relying on a single chat thread’s memory.

OpenClaw (Alt interface effort): One solo builder describes trying (and initially abandoning) the idea of making a better OpenClaw UI than Telegram/Discord, then “wrestling with it for like 40 days” and now building an alternative interface aimed at broader users with less config, according to the Progress note.

The practical takeaway is that “agents over chat” is starting to get treated as a UI primitive—but the default shells (Telegram/Discord) are being experienced as a ceiling for non-tinkerers.

OpenClaw (Use-case library prompt): A Turkish-language prompt asks active OpenClaw users to explain why and for what purpose they use it—explicitly to seed ideas for others, as written in the Community question.

This is a small signal, but it’s how “agent OS” tools usually mature in creator circles: shared, copyable task recipes (capture → transform → file away) start to matter more than the underlying model brand.

Nano Banana 2 in Leonardo (prompt recipe): A “night flash photography” base prompt is being used to reliably get the direct-on-camera-flash snapshot look—hard shadows, mild grain, imperfect framing—by locking in compact-camera language and a 28–35mm wide lens spec, as written in the base prompt text.

The same thread expands it into multiple ready-to-run scene variants (parking garage, street phone, rooftop, neon graffiti), and explicitly calls out that the images were made inside Leonardo, as stated in the Leonardo usage note alongside the Leonardo app link in Leonardo platform.

Workflow template (prompt packaging): A creator workflow is being promoted as “7 .jpg files / 7 prompts = ‘above-AI’ videos,” organized as a repeatable project folder (Prompts, brand-name swap, JPEG outputs, Edit) and then assembled by dropping frames into an NLE timeline, as shown in the workflow walkthrough.

Video loads on view

The follow-up post adds the exact sequence (generate images, import, arrange frames, add SFX, render), as spelled out in the step list.

Nano Banana 2 (prompt pattern): A concrete “scene → model sheet” technique is circulating for producing character turnarounds (front/side/back/face close-up) by referencing a turnaround template image and asking the model to recreate a target character in that format, per the prompt text in the turnaround prompt example.

This matters for concept-to-production handoff: turnarounds are the missing bridge between pretty single frames and downstream workflows like rigging, 3D blocking, and consistent video characters.

Midjourney (SREF analysis): Promptsref posted a full style teardown for a top-performing SREF combo—--sref 3925989607 1215797590 --niji 7 --sv 6—characterizing it as a graphic-novel × cyberpunk manhwa hybrid with bold outlines and cel-shaded hard shadows, as written in the style analysis post.

The post also lists practical usage scenarios (character concept sheets, motion comics, streetwear branding) and points to a prompt library on their site, as linked in Sref library page.

Midjourney (style reference): A “cinematic hand-painted” 90s anime look is being shared as a single SREF code—--sref 2815259389—explicitly framed as Ghibli-influenced and close to films like Nausicaä, Mononoke, and Castle in the Sky, per the Sref note.

Because it’s a single code drop rather than a long prompt, it’s easy to slot into existing character/world prompts without rewriting the whole description.

Midjourney (style reference): A warm, film-like portrait look is being packaged as a single style recipe—--sref 4012673573 --v 7 --sv 6—with claimed traits like film grain, soft natural light, and golden tones, plus notes that it extends beyond portraits into lifestyle/fashion/book-cover imagery, as described in the Sref recipe post.

The linked sref guide in Sref guide suggests this is being formalized into a reusable prompt formula, not just a one-off code drop.

Nano Banana (prompt pattern): A reusable “Notion-styled portrait” recipe is being shared as a fast way to generate cohesive profile-icon packs by changing only 1 variable at a time—so you can keep a stable look while swapping hair, clothing, expression, or lighting, as summarized in the Notion icons explainer.

The shared framing is explicitly asset-factory oriented (“Hit Generate, get unlimited assets”), which maps well to pitch decks, UI kits, and internal tools where consistency matters more than photorealism, as shown in the reshared graphic.

Nano Banana Pro (prompt schema): A copy/paste JSON prompt called “Noir Techcore” is being shared for product renders that force clean framing rules (centered, no cropping) and a high-contrast look (black background, dramatic rim lighting, orange internal glow), with explicit “no text/logos/watermarks/stands” constraints in the Noir Techcore prompt.

The schema approach is the point: it’s a template where you only swap [INSERT_PRODUCT_HERE] and keep the constraints stable to avoid typical ad-mockup failures (clipped edges, phantom typography, unwanted props).

Smart Mesh (Tripo): Tripo’s Smart Mesh (inside Tripo P1) is being pitched as a production-focused 3D generator that outputs “clean topology” meshes in about 2 seconds, explicitly framed as skipping retopology/cleanup work in game pipelines, as described in the GDC Smart Mesh breakdown and reiterated in the P1 feature framing. Posts also claim the feature is now live post-GDC, per the Smart Mesh live note, alongside floor-level demand signals like “studio leads and technical artists” asking pipeline questions in the GDC booth signal.

Video loads on view

• Pipeline positioning: The messaging emphasizes “structured 3D meshes with clean topology” for real-time/game workflows rather than novelty renders, as stated in the P1 feature framing.
• Availability signal: The “GDC is done. Smart Mesh is live” line is the concrete shipping claim, as posted in the Smart Mesh live note with a pointer to the Product page.
• Adoption heat: The booth-crowd anecdote (integration questions all week at Moscone) functions as early market validation for studios, as reported in the GDC booth signal.

Prompt-to-print accessories (Meshy): Meshy is showcasing a direct “photo/prompt → printable object” flow using a pet as the source image and outputting an accessory-scale 3D model (example: corgi earrings), compressing character/object modeling into a single generation step, as shown in the Pet earrings demo.

Video loads on view

The demo format matters because it’s explicitly framed around a “printable 3D model,” not just a render—i.e., the output is positioned as merch-ready geometry rather than concept art, per the Pet earrings demo.

Concept-to-asset translation: A side-by-side from 0xInk shows a stylized mech-walker concept image and a corresponding physical-looking 3D figure render (same pose/silhouette details), illustrating a workflow where a single concept frame can anchor downstream 3D assetization, as shown in the Concept-to-3D comparison.

The key creator implication is consistency: the output reads like something that could move into packaging shots, store listings, or a game asset review pass because the “final” looks less like an illustration and more like a manufactured object, per the Concept-to-3D comparison.

3D generation paradigm shift (discussion): A shared take argues for building 3D “from semantics” rather than starting with coarse geometry, positioning semantics as the primary representation and geometry as a derived artifact, as summarized in the Semantics-first 3D take.

This is showing up as a creator-relevant research signal because “semantics-first” implies workflows where prompting/labeling could control topology/part structure more directly than today’s mesh-from-image approaches, per the Semantics-first 3D take.

Seedance 2.0 (ByteDance): A new “stress test” style clip frames train fight scenes—tight interiors, fast limbs, collisions, moving background parallax—as something that was “practically impossible” before, but now looks plausible with Seedance 2.0, per the train fight claim.

Video loads on view

The value for directors is the shot type itself: lots of occlusion and rapid camera-relative motion, so you can quickly see whether a model holds body coherence, contact timing, and scene continuity across cuts, as demonstrated in the train fight claim.

Seedance 2.0 + Midjourney SREF: Creators are pairing a fixed Midjourney aesthetic anchor—--sref 2156543800—with Seedance 2.0 to generate a consistent “post‑apocalyptic wasteland” vibe, as shown in the wasteland pairing demo and echoed by the alternate example.

Video loads on view

The SREF itself is documented with a longer style analysis in the linked Style breakdown, which is being used as a reference when dialing in the look before animation.

Seedance 2.0 (ByteDance): A practical experiment uses Seedance 2.0 to animate an older Midjourney image, explicitly treating it as a fidelity check for whether the model preserves the original still’s look while adding motion, per the Seedance experiment note.

Video loads on view

A second short clip in the same thread reinforces the “old still → motion” test idea, as shown in the follow-up clip.

PixVerse V6 (PixVerse): A new PixVerse V6 model selection card is shown in-app with “NEW” labeling and a “20s” duration indicator, claiming native audio, “directorial cinematography,” and “true‑to‑life physics,” per the PixVerse V6 screenshot.

The tweet is a heads-up rather than an evaluation—no public settings breakdown or side-by-side results are included in the PixVerse V6 screenshot.

AI filmmaking pulse: A “This Week in AI Filmmaking” thread packages March 17–22 as a single checklist across policy, editing, world models, and post work, starting from the weekly recap list.

Video loads on view

• Open research that maps to film workflows: The thread highlights InSpatio‑WorldFM as a single‑photo to navigable 3D world model, shown in the world model demo, plus SparkVSR’s user-steered super‑resolution idea, demonstrated in the super-resolution demo.
• Editing/VFX building blocks: It flags SAMA as an instruction‑guided video editing model with examples in the SAMA demo, and EffectErase for object removal/insertion with a longer visual demo in the EffectErase demo.

Treat the roundup as a curation layer—many items have clips, but no unified benchmark artifact is provided in the weekly recap list.

Codex desktop app (OpenAI): A creator reports running “all the dev projects” on a remote Mac Studio and steering it “from anywhere,” calling the remote connection stable even when away, as described in the Remote Mac Studio workflow. Short version: local laptop becomes the console; the heavy lifting stays on the workstation.

The shared UI shows a live environment with “3 background agents” and a connected target (“macstudio alpha”), plus a thread-based workflow and file-change summary, as captured in the Remote Mac Studio workflow.

Codex (OpenAI): A prominent day-to-day user says they’ve been on Codex since “around August–September” and that it “feels like talking to a serious adult and coding with a senior,” contrasting other tools as feeling like “a golden retriever,” per the Codex daily-driver take. This is less about benchmarks and more about developer UX: perceived rigor, tone, and reliability during long implementation sessions.

The same post notes they still sample other models “for UI here and there,” but default back to Codex for most work, as described in the Codex daily-driver take.

Claude Code ecosystem: “Best GitHub repos for Claude code” listicles are re-circulating as a discovery mechanism, with Superpowers repeatedly positioned as a go-to framework for agentic dev workflows in the Repo listicle snippet.

In the linked GitHub repo, Superpowers is described as a composable “skills” framework + methodology that can plug into Claude/Cursor/Codex/OpenCode setups, and it’s sitting at 105k+ stars per the GitHub repo.

Codex desktop app (OpenAI): Theme customization is showing up as a practical “stay in the tool all day” affordance, with one user calling out the app’s theme options and sharing a screenshot of the Appearance panel in the Theme screenshot callout.

The settings shown include explicit controls like an accent hex value, a contrast slider, and a translucent sidebar toggle, as visible in the Theme screenshot callout.

Tinkerer Club (community infra): The founder says they bought tinkererclub.com “for a stupid amount of money” and is explicitly testing whether “.com means 10x revenue,” per the Domain purchase note. It’s a creator-business move wrapped around an automation + self-hosting identity.

On the site, Tinkerer Club is positioned as a paid community around automation/digital sovereignty with 800+ members and member tooling spanning Claude/Codex-style AI, Docker, n8n, Home Assistant, and ESP32 projects, as summarized on the Community page.

Screenpipe (screenpipe): An open-source “AI memory” layer is getting shared again—Screenpipe continuously records your screen and audio locally, lets you query it with natural-language search, and plugs into tools like Claude/Cursor/ChatGPT through MCP, as described in the feature overview.

Video loads on view

The project positioning is explicitly privacy-forward (“local” capture rather than cloud upload), and the repo notes concrete operating costs—on the order of ~5–10% CPU, ~0.5–3GB RAM, and ~20GB/month storage—per the GitHub repo.

Typeless (Typeless): Typeless is being pitched as a typing replacement on Windows with a v1.0 release, claiming ~220 words per minute from natural speech while removing filler words/repetition, auto-formatting text, and adapting tone per app (casual chat vs professional email), as stated in the Windows launch thread.

Video loads on view

The privacy bundle is central: the thread claims “zero cloud retention,” “never trained on your voice,” and local history, all in the same Windows launch thread.

Skales (Skales): The “desktop agent for non-terminal users” storyline is re-circulating, with one post claiming Skales can run a full AI agent on a desktop “without touching a terminal” and with a very low-memory footprint (around 300MB RAM), as quoted in the recirculated claim.

What’s missing in the tweet is the concrete surface area (what apps it can control, what permissions it needs, and what data stays local), so treat it as a capability claim rather than a fully specified release.

Google Stitch (Google): Stitch is getting framed as a UI “thinking tool vs making tool,” where prompt-based edits automatically fork the design so you can compare the evolution side-by-side, as described in the Thinking tool framing.

The same post highlights a canvas that mixes text notes, generated screens, reference images, and a lightweight design system, plus fluid device previews (phone/tablet/web) and an embeddable prototype directly on the canvas, per the Thinking tool framing. The positioning is explicitly “upstream from Figma”—more about structuring exploration than polishing comps.

Google Workspace flows (Google): Google is rolling out Zapier-like automation inside Workspace—users can pick preset workflows (for example, “get pre-meeting briefings in Chat”) or type a request to generate a custom workflow (for example, “summarize changes across my docs daily”), as shown in the Flows launch post.

Video loads on view

A notable UX point in the same thread is that the hard part for most people is deciding what to automate; the author specifically calls out interest in Google inferring and auto-building workflow suggestions from a user’s activity over time, per the Flows launch post.

Google Flight Deals (Google): A “Google Flight Deals (Beta)” feature is being shared as a quick way to browse/track flight prices in a swipe-friendly flow, per the Beta feature clip.

Video loads on view

For working creatives, this reads less like “AI generation” and more like a time-saver inside a tool many already use (trip scouting, festival travel, client shoots), with the post explicitly treating it as something worth trying before it potentially gets restricted or changed, according to the Beta feature clip.

Hugging Face Spaces (Hugging Face): Spaces now supports a Protected visibility mode—users can keep the Space’s repo private while the app remains usable via its public URL, per the feature announcement; the same settings panel also introduces custom domains for hosting a Space behind your own DNS name.

• Protected mode: The UI copy emphasizes “anyone can use the app directly, but only you can view or commit to the repository,” which is a clean way to ship client-facing demos without exposing prompts, code, or wiring, as shown in the feature announcement.
• Custom domains: The “Custom domain (NEW)” field appears alongside visibility controls, enabling portfolio-style hosting and production-ish front doors without leaving Spaces, per the feature announcement.

Open OCR on Hugging Face: OCR model releases are being called out as arriving in a burst, with dots.mocr (renamed from dots.ocr 1.5) noted as taking #2 on OlmOCRBench, per the OCR leaderboard note.

For creative teams, this is a hub-watching cue: OCR checkpoints are landing fast enough that ‘which OCR to deploy’ is turning into a rolling benchmark conversation rather than a one-off tool choice, per the OCR leaderboard note.

Indie shipping on Hugging Face: A viral repost spotlights a single individual who reportedly has “29 models on Hugging Face” appearing in ranking pages—framed explicitly as “no lab… no sponsorship,” and funded with “$2,000” of personal GPU spend in the ranking anecdote.

This reads less like a specific model launch and more like a distribution signal: the hub’s leaderboards can surface sustained solo output at scale, per the ranking anecdote.

MiniMaxAI (MiniMax): A “time to follow” post points creators at MiniMax’s Hugging Face organization, with the org feed showing active paper submissions and recent model activity, as seen in the org screenshot and linked via the Org page.

The practical value here is feedwatch: for creators tracking image/video/model drops, following the org is a low-effort way to catch releases as they land on the hub, per the org screenshot.

Hugging Face Papers (community feed): The “most upvoted papers this week (March 16–22)” roundup format is being used as a quick filter for what’s rising on the hub, per the weekly list.

This is less about any single paper and more about distribution mechanics: when the Papers feed becomes the default pulse, creators can treat upvotes as an early-warning system for what’s likely to get implementations, demos, and Spaces next, as implied by the weekly list.

Seedance 2.0 (ByteDance): A Turkish thread claims US senators Blackburn and Welch sent a letter urging ByteDance to shut the model down over alleged Hollywood IP theft in viral clips, with a “global launch” reportedly paused under US pressure, as summarized in the [Turkey recap](t:88|Turkey recap).

• China-first distribution signal: The same post says China is moving the other direction—Seedance 2.0 is described as integrated into Xiaoyunque via a “Short Drama Agent” that takes a script and outputs characters, voice, storyboards, and scene-by-scene video, per the [same recap](t:88|Turkey recap).
• Access + enforcement reality: It also claims most access outside China is via third parties or VPN, and that attempts often fail due to copyright/permission filters, again per the [usage note](t:88|usage note).

Net: creators get a clear split-screen—policy/IP constraints shaping western availability while productization accelerates domestically.

YouTube training data (Google): A filmmaking roundup thread claims Google confirmed training Gemini 3 and Veo 3 on roughly 20 billion YouTube videos and frames it as “zero opt-out,” linking it to likeness exposure concerns for creators, per the [training controversy claim](t:260|training controversy claim).

The same post cites an anecdote that a text-only prompt produced near-identical imagery of a specific YouTube creator (presented as “overfitting”), which is being used as a rhetorical proof point for why performers and internet personalities feel uniquely exposed by video-scale training, as described in the [same claim](t:260|same claim).

Copyright (US): A recurring creator-to-creator claim—“AI art can’t be copyrighted”—is getting called out as a misread of actual guidance and rulings, with the emphasis being that outcomes depend on the human-authored contribution and how it’s documented rather than on a blanket ban, as argued in the [rulings pushback](t:44|rulings pushback).

The practical implication for working artists is less about winning internet arguments and more about being precise: what you selected, arranged, edited, or materially transformed is the part you can typically defend as authorship—even if a model helped generate ingredients.

AI-as-tool framing: A popular rebuttal to “you didn’t do anything, the AI did it” compares generative models to traditional creative tools (pencil/brush/chisel/camera) and argues that dismissing tool-assisted work would imply only unexpressed ideas count as art, as laid out in the [tool analogy post](t:14|tool analogy post).

This matters in practice because it’s the same argument pattern that shows up in crediting, contracts, and platform disputes: who is the author, what counts as human contribution, and what “materialized” creative labor looks like when the last mile is model output.

dots.mocr (dots): Open OCR releases have been landing quickly on Hugging Face lately, with dots.mocr (renamed from dots.ocr 1.5) called out as taking #2 on OlmOCRBench, per the OCR leaderboard note. For AI creatives, this is the kind of quiet foundation shift that improves downstream workflows like scanning sketchbooks/storyboards, extracting text from references, and building searchable “production bibles” from PDFs and screenshots—without having to hand-clean transcripts.

Hugging Face papers pulse: The “most upvoted papers this week (March 16–22)” list includes a video-reasoning themed entry (“Demystifing Video Reasoning”) alongside other popular research threads, as surfaced in the Weekly paper list. For filmmakers and editors, this is a useful signal that video understanding (not just generation) is getting more mindshare—often a precursor to better clip search, scene labeling, and edit-assist tools that can answer questions about what’s happening across long timelines.

WAR FOREVER (Dustin Hollywood / NAKID® PICTURES): Following up on teaser campaign—multi-drop teasers for a June window—Dustin Hollywood published another short teaser cut (“SNEAK PEEK #2”) as shown in the teaser post, then pointed viewers to an HD YouTube version via the YouTube link post and framed the project as having reached “cinema grade” in a longer statement in the milestone note.

Video loads on view

The creative signal here is less about a single clip and more about release cadence: multiple short drops (X-native + YouTube HD) to build a repeatable trailer pipeline, with collaborators/tools name-checked in the teaser copy in the teaser post.

Mary’s Room (Claire Silver): Claire Silver shared concrete availability details for the installation—“1/1” including a 5-day screen recording, an Edwardian telephone retrofit, a plotter, and “400 ft” of printed thoughts/drawings—plus edition counts (“10 each of 10”), as described in the Basel availability note and contextualized by the narrative setup in the project description.

The project page is linked directly via the project page, with an additional synopsis thread continuing in the installation overview.

NAKIDpictures + stages_ai: The team is explicitly pitching a workflow where a film’s story beats get translated into “consistent and IP driven gameplay development,” backed by a longer gameplay showcase clip in the workflow explainer and an additional branding/tech reel in the pipeline montage.

Video loads on view

• Throughput claim: One concrete timing datapoint shows up when the creator says a “10-minute example” took “1.5 hrs” to produce as described in the workflow explainer.
• Positioning: They call out “consistency structures” and “gameplay from a film” as the point, as stated in the consistency note.

This reads like a creator-led attempt to productize an IP bible into playable missions, not a one-off trailer.

CODEYWOOD (Kaigani): A new demo asks “Can Claude Code create an entire animated short episode?” and publishes an Episode 1 montage as shown in the CODEYWOOD demo.

Video loads on view

The post frames this as episodic animation experimentation rather than a single clip, with the broader thesis (“AI is creating an all-encompassing cultural cinematic universe”) echoed in the CODEYWOOD demo.

‘THIS IS FUCKING ART’ (Dustin Hollywood): The coffee-table book rollout continued with additional page/image previews—ranging from high-contrast equestrian imagery to fashion/editorial scenes—shared across multiple posts like the book preview post and the liminal interior preview.

A separate note says the “final images” are locked and pages will start shipping soon, as stated in the final images note.

Product surface thesis: The claim is that once AI can reliably generate small features on demand, every app/site becomes its own “App Store” surface—users effectively commission custom mini-apps inside the product instead of downloading separate software, as argued in the App store thesis.

That matters to AI creatives because the “distribution unit” becomes the tool you already use (editor, DAW, canvas, CMS), which changes where creators sell value: not just finished content, but reusable in-product automations, templates, and agent behaviors that live inside the workflow.

Acquisition pattern: A concrete CAC reframing is circulating: instead of paying for ads that get more expensive, consumer AI products can treat free inference as the non-inflationary equivalent of “give a stock / get a stock,” i.e., you directly give the user what you would’ve spent acquiring them, as argued in the Free inference as CAC.

The key claim is that this works best when the free usage credibly seeds a habit loop (so the giveaway kickstarts recurring usage), rather than acting as a one-off coupon—framed explicitly as “effectively gave the customer the CAC” in the Free inference as CAC.

Consumer growth economics: Following up on Paid ads signal (paid ads as PMF warning), the thread narrows the claim to “generational consumer companies” targeting $10B–$20B+ outcomes, arguing growth that’s 50%+ paid ads for long stretches tends to be harder to sustain because ad costs inflate with scale, as detailed in the Discourse clarification.

• Network effects lens: The biggest consumer outcomes are framed as network-effects businesses (social/marketplaces), where organic growth is treated as proof the value proposition compounds without continuously buying users, per the Discourse clarification.
• AI exception teased: The same post floats a change specific to AI products—mainstream users may become more willing to directly pay for software—which could weaken the historical “ads cap your upside” heuristic, according to the Discourse clarification.

Brand infrastructure: One creator reports buying the tinkererclub.com domain “for a stupid amount of money,” explicitly to test the hypothesis that “dot com means 10x revenue,” as stated in the Domain purchase note.

The adjacent business context is a paid community positioned around automation/self-hosting and AI tooling; the public pricing range is $99–$399 with a shown “current pricing” of $299, per the Membership page.

Mary’s Room (Claire Silver): A Basel availability note spells out the work’s collectable structure—one 1/1 package includes “screen+recording of all 5 days,” a handmade driftwood frame, laser-cut brass derived from an AI image, an Edwardian telephone retrofit as headset, a plotter, and “400 ft” of printed output, as detailed in the Basel availability note. The same post also states there are “editions: 10 each of 10,” with “digital+print on request,” and points to the project page via the project page.

• What matters for IRL context: It’s a rare case where the installation mechanics (live capture → plotter output → physical artifact) are explicitly productized for Basel collecting, rather than remaining a one-off documentation bundle, per the Basel availability note.

Mary’s Room (Claire Silver): A public reminder says the Art Basel Hong Kong presentation is now “less than 4 days” away, positioning the work as an imminent IRL stop for AI-native installation audiences, per the countdown note. The surrounding thread frames the piece as a 5-day continuous writing/sketching performance mediated by live feeds and a retrofitted Edwardian telephone—an AI-era twist on the qualia thought experiment—according to the project description and installation setup.

The post doesn’t include booth details or ticketing logistics, so the practical “go see it” info still hinges on whatever the on-site program lists.