Octomind adds image and voice support, refuses queries when model lacks vision

·2 views

Developer tool Octomind has shipped a new update introducing image attachments and voice input across browser, Telegram, Slack, and WhatsApp sessions. Unlike most AI tools that silently strip unsupported images and respond anyway, Octomind explicitly refuses such requests upfront and names a compatible model instead. Voice input includes safeguards like a 15-second silence cutoff, a two-minute hard stop, and a minimum three-word threshold before any query is sent. All inputs — screenshots, voice notes, or typed messages — share a single persistent session across devices, with no re-uploading needed after model switches. Images are available on all plans at no extra cost, while voice features are limited to paid plans at $0.010 per minute to listen and $0.025 per minute to speak.

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 One Developer Built Cookieless Mobile UX Tracking on Cloudflare D1

A developer running a small emergency locksmith website in southern Germany built a custom, cookieless mobile UX measurement tool after noticing visitors were reaching the phone number page but not calling. The system uses a single Cloudflare Pages Function, a D1 database table, and an inline script — requiring no cookies, localStorage, or consent banners. A key technical challenge was accurately detecting real taps versus scrolls, solved by filtering pointer events that move more than 12 pixels or last longer than 600 milliseconds. The tool also logs 'dead taps' — touches on non-interactive elements — which helped uncover a conversion issue where a styled phone number lacked a clickable tel: link. Pinch-zoom events are recorded with page position context, turning vague usability signals into specific, actionable insights tied to content location on the page.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Well-Structured Codebases Help AI Coding Tools Perform Better, Developers Warned

As AI coding assistants like GitHub Copilot, Cursor, and Claude Code grow more capable of editing files and implementing features autonomously, developers are being urged to treat their entire codebase as part of the AI's working context. Poorly organised repositories — with scattered files, vague naming, and minimal documentation — cause AI agents to guess at project structure, often duplicating logic or modifying the wrong files. Experts recommend organising code around features rather than generic utility folders, so AI tools can immediately locate relevant logic without unnecessary exploration. Descriptive file naming, such as 'stripe-webhook.handler.ts' instead of 'helper.ts', provides semantic clues that AI models rely on to generate accurate, consistent code. A clear README explaining project architecture further reduces errors by giving AI agents a reliable map of how the application is built.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Silent AI Agent Failures Are More Dangerous Than Loud Crashes

A developer building AI agents near real systems warns that the most dangerous failure mode is not a crash but a silent false success. In these cases, the agent appears to complete a task and the UI confirms it, yet the underlying command never ran, ran incorrectly, or validated its own assumptions rather than actual system state. The author argues that isolation alone is insufficient as a safety measure for agentic systems. The more critical question, they contend, is whether engineers can fully reconstruct what was executed — including the command, arguments, timestamp, and outcome. The post invites practitioners who have deployed agents near live systems to share how they detect these invisible failures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Apify Actor audits GitHub Markdown links and files issues without cloning the repo

A developer built a GitHub Documentation Link Auditor using an Apify Actor and an MCP connector that reads Markdown files directly from GitHub without cloning the repository or storing credentials in the Actor input. The tool checks up to 100 public HTTP links per run and creates or updates a single marker-owned GitHub issue with its findings, avoiding the noise of repeated daily issue creation. On August 9, 2026, the Actor was tested twice against a public fixture, successfully identifying one broken 404 link, one rejected loopback URL, and two reachable links across both runs. The workflow uses two separate MCP connector inputs — one read-only and one write-only — so dry runs do not require write permissions, and the Actor never gains access to branch, pull-request, or file-editing tools. The approach inverts the typical Apify MCP pattern, where an external AI client calls Actors as tools, instead having the Actor call a third-party service at two narrow points in its pipeline.

0 comments Read more at DEV Community