A chatbot
- Answers one question at a time
- Waits for you to do the next step
- Gives you text to copy and use
Technology · 23 Oct 2026 · 5 min read
An AI agent is an assistant that does not only answer your question, but also does the work. You give it a goal, and it plans the steps, uses tools, checks the result and tries again if something fails. This is how I understood it as a designer with no engineering background, and how I now use it.
Most of us first met AI as a chat box. You type a question, it types an answer, and then you go and do the work yourself.
An agent closes that gap. Think of the difference between asking a friend for directions and asking a driver to take you there.
Almost every agent follows the same simple loop, which is also how a person works on a task.
The tools are the part that surprised me. An agent can open files, write and run code, search the web or use other apps, so that it does the task in front of you, not just talks about it. "Agentic AI" is simply the name for AI systems that work this way.
I did not learn it from a course. I learned by using an agent to build the website you are reading.
I am a designer, and this portfolio was my first serious front-end build. I described what I wanted in plain words: add my IIT Guwahati projects to the playground, remove a section, update my links. The agent read the project, changed the files, ran the site to check it and showed me screenshots. When something broke, it read the error and fixed it.
Four things I learned along the way:
Vague requests gave vague results. "Make it look good" worked far less well than "keep my text and images as they are, but present them in a minimalist layout".
It did its best work when I attached my actual PDFs and files instead of describing them.
I treated each change like a design review. I looked, said what felt off, and it adjusted.
It can build quickly, but taste, order, wording and what is true about my work are still mine to check.
None of this needs you to become an engineer. Some places where it fits a designer's day:
Collect and compare sources, read long documents and summarise what matters, so you can spend time on judgement.
Turn a sketch or a described flow into a working page you can click through and test with people.
Rename files, resize image sets, convert formats or tidy a content library.
Hand over a clear spec, or build the first version of a component yourself and refine it.
Draft case study outlines and captions from your own notes, then rewrite them in your voice.
Ask it to test a page at different screen sizes or look for broken links before you publish.
For me, it is a patient collaborator that handles the parts I cannot do yet.
Pick one small, real task, such as turning a PDF into a simple page. Describe the goal clearly, give it your files and review each step. You will learn more in an afternoon than from reading about it.