Sitelas Lets You Manage Your Website Entirely Through Claude Chat

·2 views

Sitelas is a website platform that integrates with Claude AI via a Model Context Protocol (MCP) connector, allowing users to build and manage their sites through a single chat interface. Once the connector is added to Claude, users can publish pages, read form submissions, and make edits without logging into a separate dashboard. Form submissions are automatically captured to an inbox that Claude can read directly, enabling users to surface leads and draft replies within the same conversation. Site edits are shown as a preview first, with the live page only updated when the user explicitly approves the changes. The platform also works alongside other Claude connectors, such as Google Sheets, letting users automate tasks like logging leads by simply asking Claude to do so.

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)

How to build a rate-limit backstop for AI agents that send bulk emails

AI email agents operating in loops can silently exhaust daily send quotas, leaving batches only partially delivered with no record of which messages went out. Unlike humans, agents do not pause before sending and can fire hundreds of requests within minutes, triggering HTTP 429 errors mid-task. The recommended fix is a client-side backstop consisting of a token bucket throttle, an overflow queue, and a retry loop with backoff, keeping send rates below the provider-enforced ceiling. On Nylas's Free plan, each Agent Account is limited to 200 sends per day, a quota shared across API messages, drafts, and calendar invitations alike. Notably, exceeding the quota causes email sends to fail loudly with a 429 error, while calendar invitation sends fail silently, making it critical to account for both in any robust implementation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a Calendar Conflict-Resolution Agent Using Nylas API

Double-booking conflicts occur when two calendar requests land within seconds of each other, both passing availability checks and creating overlapping events that go unnoticed until a meeting begins. A developer tutorial from the Nylas team outlines how to build an AI agent that owns its own calendar account — called an Agent Account — to detect and resolve such clashes automatically. The agent monitors its calendar for overlapping events, applies a configurable rule to determine which event takes priority, reschedules the losing event, and emails affected participants to renegotiate. Unlike typical AI scheduling demos that only handle open-slot booking, this approach tackles the harder post-booking conflict problem without any human intervention. The setup requires a registered domain, a Nylas API key, and a single API call to provision the agent's dedicated mailbox and calendar.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

agents.design Offers Curated UI Resources to Help AI Coding Tools Produce Distinct Designs

A new platform called agents.design has launched to address the repetitive, generic UI outputs commonly produced by AI coding tools such as Cursor, Claude Code, Codex, v0, Bolt, and Lovable. The platform provides a curated gallery of design resources, including DESIGN.md specification files and copy-paste prompts tailored specifically for AI coding agents. Users can browse designs that suit their product's aesthetic, then paste the accompanying prompts or templates directly into their preferred AI coding tool. The core argument behind the platform is that AI tools are capable implementers but lack design judgment unless given structured constraints and a real design system. A free tier allows access to select templates, while a paid option unlocks the full catalog of components and specifications.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

iOS 26 adds post-quantum ML-DSA keys in Secure Enclave; Android support remains partial

Apple's iOS 26 introduced hardware-backed ML-DSA post-quantum signing keys inside the Secure Enclave, using a familiar CryptoKit API that ties biometric authentication directly to the key rather than app logic. A developer building a cross-platform Capacitor plugin found iOS support straightforward, with private keys never leaving the device's secure processor. Android's Keystore similarly supports ML-DSA key generation with per-operation biometric authentication, offering comparable signing capabilities. However, Android does not expose ML-KEM, the post-quantum key encapsulation standard, to app-level code through the Keystore API, despite the algorithm being present in the device's secure hardware. This gap forces developers to implement ML-KEM in software on Android, requiring extra steps to protect the private key by encrypting it with a hardware-backed, auth-gated Keystore key.

0 comments Read more at DEV Community