In regards to that specific terminology, NO, an AI agent is:
a call to an Large Language Model endpoint either locally or on an external server.
It does not exist independently, it has no memory, it cannot be domain-locked, it cannot be hardware-aware, etc. It is just a black box that you send your prompt/conversation/data too, and it outputs data in return.
In regards to your concept YES. You can build:
- A safe, domain-locked, hardware-aware ENVIRONMENT AND APPLICATION that you then CONNECT TO AN LLM.
The AI or “agent” itself has nothing to do with your program, your hardware, your memory retention, your safety features, etc. The “AI Agent” (LLM), is just an endpoint that you integrate into your application. This is the most common misconception and misapplication of terminology today in regards to AI. The AI Agent is not the “doer” - the program/application/environment that you build for it to interact with is the “doer”.
The AI Agent is just “one service of a multifaceted program/application” that provides the generative-text layer for achieving the users end-goals.
So you have to decide:
- How your going to save data and build a store/database of information/conversation history/etc.
- How your going to “configure” and “save” (for this project and or extensible for future projects) your “environment configuration” (i.e. your hardware specifics, etc.).
- How your going to connect external tools (i.e. to the car computer)/data/etc. and save that/maintain it/etc.
- How your going to contact the LLM/AI endpoint (i.e. using API, or using existing web interfaces like chat GPT, etc.).
Making use of existing interfaces like OpenAI/ChatGPT conversation history, “memory” features, etc., means you are limited completely to their interface, though with development of MCP (Model Context Protocol) that’s extended a bit now.
But their environments (I.e. chatGPT) are also non-specific, and you cannot guarantee safety or reliability in this way, because their tools are general purpose and not specific-to-your-use-case.
In this circumstance, I would recommend that you:
- Develop a standalone application, most likely one that would involve a cross-device interface (like a web app, or a native app that can run both on smartphone and on laptop) so that you could actually use the app from whatever device you happened to wanted to plug your car-computer-reader-whatever into. This way you can control the environment, the memory, the integration with the LLM, etc. Otherwise, you are trying to bootstrap someone elses “app that’s built for coding and conversation” into a “hardware-specific and real-world-impacting” circumstance that frankly, would be definitely unsafe!