Charming platform lets AI-built Claude apps get a permanent URL and database

·1 views

A tool called Charming allows apps built by Anthropic's Claude AI assistant to be hosted with a persistent URL and data storage, rather than disappearing when the chat session ends. Users connect Charming to Claude as a custom MCP connector, then instruct Claude to deploy the app to Charming, which returns a live URL backed by key-value storage. The setup requires a one-time configuration at claude.ai and enables Claude to author and publish a self-contained JavaScript module that defines the app's routes and data handling. Once hosted, the app's data persists across sessions and can be accessed or modified by other AI agents via MCP or standard HTTP calls. A working demo — a reading list app — is publicly available, and the full setup guide and source code have been published by the Charming team.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds unofficial 55-second launch video for Claude Opus 5

An independent developer created an unsolicited 55-second promotional video to mark the launch of Anthropic's Claude Opus 5 model. The video was built entirely using visual assets, colors, and typography sourced directly from Anthropic's own website and official launch post, with no elements redrawn or invented. It highlights key product claims, including benchmark performance and pricing, using Claude's actual brand palette and typefaces. The project involved precise motion design across twelve structured segments, covering everything from benchmark comparisons to pricing and agent capabilities. No commission or brief was involved — the creator made it purely as a self-initiated design exercise.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agent memory flaw: AI knows your rules but ignores them when it matters

A developer identified a subtle but significant failure mode in AI agent memory systems where stored user preferences are never actually applied during relevant actions. The problem stems from how memory retrieval works: similarity search matches queries to stored facts by semantic meaning, so a rule about commit style is never surfaced when the agent processes an unrelated command like 'fix the login bug.' Common workarounds — pinning all rules to every prompt or storing them in static config files — introduce token bloat or go stale over time. The proposed fix introduces a third retrieval method called recall_for_action, which tags preferences with the specific action they govern, such as trigger:git-commit, and fetches them deterministically at the exact moment that action runs. This approach avoids embedding-based search entirely, making retrieval fast and reliable precisely when it is most critical.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Context Compression Helps AI Agents Stay Efficient Without Losing Key Insights

As AI agents tackle complex tasks like debugging API errors, they can accumulate tens of thousands of tokens of context across dozens of tool calls, much of which becomes redundant over time. This growing context window raises costs, slows processing, and can crowd out newer, more relevant information. Context compression addresses this by retaining only the conclusions and current state of an investigation, rather than every intermediate step. Two core techniques — pruning, which removes no-longer-relevant data, and distillation, which converts lengthy histories into structured summaries — help agents stay focused and efficient. The approach allows agents to continue working effectively without carrying the full weight of their investigative history forward.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer ships three browser-based AI tools, documents bugs found along the way

A developer built WeConvertIt, a platform offering image, PDF, and audio tools — including background removal, stem separation, and speech-to-text — that run entirely in the browser without uploading files to a server. During development, a stem-splitting tool using Meta's HTDemucs model produced physically impossible output, with some audio stems exceeding 174% of the original signal's magnitude, which revealed the third-party ONNX model file itself was defective rather than the pipeline code. The developer resolved this by exporting a fresh ONNX model from the official checkpoint and validating it against a reference implementation before shipping. A separate bug in ONNX Runtime caused outright session failures in the Whisper-based speech-to-text feature due to tied embeddings in quantized models, an upstream issue beyond the developer's direct control. A third challenge involved browser memory limits surfacing only on longer audio files, highlighting the unique constraints of running AI models entirely client-side.

0 comments Read more at DEV Community