Developer builds persistent memory system for Mac AI coding app Deiko

·3 views

A developer building Deiko, a Mac app that captures screen context and voice input for AI coding agents, grew frustrated that agents had no memory of previous debugging sessions on the same issue. After noticing repeated explanations of identical bugs across days, he spent a week engineering a memory layer to let Deiko recognize when new briefs relate to past tasks. He evaluated Jev, a probability-focused model from TypeSafe AI priced at $0.042 per million input tokens, which returns a confidence score on whether two items are related rather than a verbose response. When TypeSafe paused signups, he rerouted through gateways including Vercel AI Gateway, OpenRouter, and Cloudflare to access the same model. Drawing on how tools like Claude Code, Mem0, and Sentry handle memory and issue grouping, he built a small filing algorithm that combines exact contextual clues with model-based classification to cluster related briefs automatically.

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)

OpenAI Codex Suffers Full Service Outage

OpenAI's Codex service experienced a full outage, as officially acknowledged on the company's status page. The incident was identified and logged under a dedicated incident report. The disruption affected users relying on Codex for AI-assisted coding tasks. OpenAI's status page confirmed the issue was recognized, though details on the root cause and resolution timeline were limited in the available information.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How Digital Footprint Tools Read Your Data and What Stays on Your Device

Digital footprint check tools analyze exported social media archives to generate privacy risk scores, drawing primarily on post history, direct messages, IP records, and linked contact details. The core scoring relies on pattern matching within tweet history to flag phone numbers, emails, addresses, and sensitive topics, while other files serve as cross-checks to strengthen or contextualize findings. Certain data categories — such as ad engagement records, follower lists, and device tokens — are deliberately excluded to avoid inflating results or involving third-party data. All parsing, file reading, and scoring processes run locally on the user's device, with post content never transmitted over the network; only post deletion requires an authorized API connection. Discrepancies between expected and reported item counts are typically explained by the archive's snapshot date or the inclusion of previously deleted content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds AI-powered gossip tabloid for RimWorld colony that must cite its sources

A developer used Claude Code to create 'The Estian Tattler,' a fictional tabloid that generates gossip stories drawn entirely from a RimWorld game save file spanning roughly 300 in-game days. The project ingested 631 records — including marriages, conversations, letters, and game messages — from a modded colony called the Tribe of Estian. Every sentence the AI reporter writes must cite specific records as evidence, and a plain TypeScript fact-checker automatically rejects any claim that names a colonist or includes a number not supported by the cited sources. Failed drafts are returned to the reporter, with stories spiked after three failed attempts, while passing drafts await human editorial approval before publication. Six editions have been published so far, with printed stories drawing on 136 of the 631 available records, and a dashboard tracks which colonists the paper has yet to cover.

0 comments Read more at DEV Community

ProgrammingHacker News ·

OpenAI Codex Experiencing Widespread Outage With API Key Errors

OpenAI's Codex service went down, displaying an incorrect API key error for users attempting to access it. The issue appeared to be widespread, with multiple users reporting the same problem on Twitter/X. The outage was notable as OpenAI's official status page did not reflect any ongoing incident at the time. The root cause of the disruption was not immediately clear, leaving users without an official explanation or estimated resolution time.

0 comments Read more at Hacker News