DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to ask weather, unit and recipe questions without an LLM with Jev Chat

Run the chat bar locally and get weather, unit conversions and recipes from tools, not model text.

Who it is forA person who wants quick everyday answers from a chat bar and does not want a language model to make up numbers or facts.

The problemChatbots can state a temperature, conversion or recipe step that no source returned. Users need answers where every value comes from a tool.

The outcomeA running local chat app that answers weather, unit and recipe questions, with every value on screen typed by the user or returned by a tool.

What you need first

  • Node 24 or later and pnpm 11 (run corepack enable to pick up the pinned version)
  • A TypeSafe API key in TYPESAFE_API_KEY, since Jev is a paid API and the app shows error replies without it
  • A terminal and a local browser on the same machine, because the API only listens on 127.0.0.1

Steps

  1. Run corepack enable to pick up the pinned pnpm version.
  2. Run pnpm install in the repo folder.
  3. Run cp .env.example .env and set TYPESAFE_API_KEY in the new file.
  4. Run pnpm dev, then open http://localhost:5173 in a browser on the same machine.
  5. Type "350F in celsius" and "What's the weather in Denver tomorrow?" and check that each reply cites tool data.

Prompt for your agent

In the jev-chat repo, copy .env.example to .env, set TYPESAFE_API_KEY to <typesafe-key>, and run pnpm dev. Send the message "350F in celsius" to the chat at http://localhost:5173 and report the reply. Verify that the reply value came from the units tool and not from model text.

Caveat. The app only works in English, and every message gets an error reply until a paid TypeSafe key is set.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page