Who it is forA developer building a travel or city-guide feature who needs answers to look like an interactive page, not plain text.
The problemPlain chat replies cannot show a route, photos and an itinerary the user can change.
The outcomeA local chat at localhost:3000 that answers a travel request with an interactive map, photographs and an editable plan.
What you need first
- Node 24
- An OpenUI Cloud (Gateway) key in THESYS_API_KEY, or any OpenAI-compatible API key set through LLM_BASE_URL, LLM_API_KEY and LLM_MODEL
- Optional: Ollama and enough memory for a local model (the README recommends 32 GB or more for the default)
Steps
- Run
cp .env.example .env - Run
npm install - Run
npm run generate:apiKeyto write THESYS_API_KEY to .env - Run
npm run dev, open http://localhost:3000 and send: I'm in San Francisco for a day, plan a sightseeing route for me
Prompt for your agent
Clone thesysdev/open-intelligent-ui, follow its Setup section, and start the dev server. Send the prompt "I'm in San Francisco for a day, plan a sightseeing route for me" to http://localhost:3000 and report whether the answer includes a Map component. Then list the component names used in src/lib/library.ts that the answer relies on.
Caveat. The street route is a road overview from the public OSRM demo server, not walking or transit directions, and the README does not promise this for production traffic.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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