SShortSingh.
Back to feed

Ankita AI adds phone access via browser pairing, no native app needed

0
·2 views

Ankita AI, a desktop assistant built by Krish Verma, can now be continued from a phone through the phone's browser rather than a dedicated app. Desktop users create a pairing code that defaults to a browser QR code or link and expires after two minutes. The phone's browser is served a fixed set of four files over HTTPS, with strict content rules, and the phone's access token is held only in the browser tab. Pairing requests are validated against host, origin, and port checks, and the desktop owner must approve within 120 seconds. Once paired, the phone shows recent conversations and saved work, with size limits and a review step before any context is sent.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Sendclap Processes Crypto Payments in USDC on Base Without Holding Funds

Sendclap moves a supporter's USDC directly from their wallet to the creator's wallet in one transaction on Base, with its 1% fee sent to a separate address in the same call. Its contract holds no balance and has no withdraw function, so there is no custodial pool of funds. The fee is capped at 1% in code, and the owner cannot raise it above that ceiling or move users' tokens. Both contracts are reportedly verified on Sourcify, and recurring memberships work through standing USDC allowances that charge only the agreed amount per period. The author notes the system is live but still has very small volume.

0
ProgrammingDEV Community ·

Guide to OCPP: How EV Chargers Talk to Central Servers

EV charging software links chargers, payments and drivers through a central platform, and the Open Charge Point Protocol (OCPP) gives chargers and servers a shared language. Maintained by the Open Charge Alliance, OCPP runs over a WebSocket connection where both sides exchange JSON messages in a fixed frame format. The guide includes a simple Node.js example that accepts charger connections and answers BootNotification requests. It outlines core messages such as Heartbeat, StatusNotification, MeterValues and remote session control. It also notes that OCPP 1.6 remains widely deployed, while OCPP 2.0.1 adds stronger security and smart charging features.

0
ProgrammingDEV Community ·

Proposed framework lets AI build app customizations within controlled limits

The article proposes a way for business users to describe application customizations in plain language, with an AI agent creating them without gaining unrestricted access to the software. Applications would expose only specific hooks, events, data, and operations that extensions may use. Proposed changes would be written in a limited intermediate language called KEIR, which is checked, compiled, and can be simulated and reviewed before activation. The author presents Keir as an open-source framework with a compiler and runtimes for Java and Node, aimed at keeping application owners in control of how extensions run. The approach is positioned as an alternative to adding every requested option to the product or letting customers build extensions outside it.

0
ProgrammingDEV Community ·

Debugging Claude Fable 5.2 Code Art: Truncated SVG, Broken Canvas, Working Render

A developer tried to get Claude Fable 5.2 to generate code-drawn art, first requesting a full Canvas page, which returned empty responses despite HTTP 200. A longer SVG attempt was cut off mid-tag when it hit the output limit. Switching to a compact request for one complete SVG under 6,000 characters produced a valid file in about 37 seconds that rendered in a browser. The author notes the result was simple, with evenly spaced houses and icon-like details, so the fix solved delivery rather than visual quality. The article's test used a village-at-dusk scene and included the full API request code for reproduction.