Urgent.News

What's breaking now, across thousands of outlets.

AI

Ask AI providers, and where your key lives

JSLab feature notes: one docs page, explained. Today: AI providers and keys . JSLab's Ask AI panel answers questions about the code in your tab and returns changes as a diff. It doesn't come with a model of its own: it uses your own key, or Ollama locally. This note is about that setup. One provider at a time Everything lives in Settings → AI . Provider starts at None , which turns AI Chat off.…

JSLab's Ask AI feature allows users to interact with AI providers and receive code changes as a diff. Users can configure the AI provider in Settings → AI, with options like Ollama (local) that does not require an API key. Ollama is a free program that runs models on a user's Mac, eliminating the need for an API key and keeping all interactions local.

To set up Ollama, users need to install and start the program themselves, then choose Ollama (Local) as the provider and save the settings. JSLab will automatically detect and display the installed Ollama models in the Model field. Users can also set a custom Base URL if needed. API keys for OpenAI, Anthropic, and Google Gemini are stored in the Keychain and sent via a request header in the AI provider's Base URL, ensuring secure communication between JSLab and the AI provider.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

How to stop prompt injections and AI hallucinations at the OS level (CBS v1.6.2 release)

Disclosure: I am the author of Cyber-Butler-Security (CBS). If you run AI Agents (like DeepSeek Harness, AstrBot, or LangChain) locally on your machine, you've probably experienced the "Oh no" moment.

  • CBS uses fail-closed approach to restrict AI access to system resources
  • TOTP Broker intercepts high-risk actions for verification
  • v1.6.2 release addresses intent mismatch, executable content, and critical file tampering

More from Tuesday 3 November →