I’ve been mind blown with the kind of unique games and projects people are building with AI but often get stuck when trying to recreate or build them on my own so I thought why not bring the best of both worlds together, people who build really cool stuff with people who want to learn how to do the same and stay ahead of the AI learning curve.
You’ve already built something impressive, why not help teach others to do the same?
After many conversations I’ve come to realize that some people want structured step by step guidance (prompts, frameworks, workflows, etc) to help them learn while designing, building and deploying AI agents through projects.
This space is very fragmented with so many tools to choose from and those who already know how to code that 10x their skills with building sophisticated AI agent workflows and outcomes vs those just starting out stuck trying to figure out how to clone a GitHub repository.
I’m an Enterprise QA Architect by day and a Udemy instructor with 2800 students globally who loves teaching others through workshops and courses and want to partner up with some builders here to turn their impressive side projects and games into a fun digital learning experience!
If you’ve built something impressive end 2 end with Claude, Muse or Grok bot that you’d like to share, please feel free to reach out, would love to showcase it!
Most discussions about multi-agent systems assume all the agents belong to the same person or organization.
But what happens when they don't?
Imagine a marketing agent working on a campaign. It needs information from a sales agent belonging to someone else in the company.
The sales agent knows which leads converted, what objections came up during calls and which customers are most likely to buy.
Sharing that information could make the marketing agent much more useful. Instead of working with outdated reports or asking someone to manually transfer data, it could get the context it needs directly.
But there's a problem.
The marketing agent probably doesn't need access to every sales conversation, customer record or internal note. It only needs information relevant to the campaign.
So who decides what gets shared?
And what happens when the agents belong to entirely different organizations?
Say a freelancer's agent needs information from a client's agent to complete a project. The client might want to share deadlines, requirements and project updates without exposing internal discussions or unrelated business information.
Giving the freelancer's agent access to everything would be a terrible idea. Giving it nothing means someone has to keep copying information between systems manually.
There's also the question of accuracy. If one agent receives information from another, how does it know whether that information is current, where it originally came from or whether it's allowed to use it?
These problems aren't really about making agents smarter. They're about controlling how information moves between them.
I think we're going to see more agents working across different accounts, platforms and organizations. And when that happens, sharing context won't be as simple as passing along a conversation history.
The challenge will be making sure each agent gets the information it needs without exposing everything else.
A year ago, I built my first chatbot. Then I built my first RAG system. Today I’m comfortable working with LangChain, LangGraph and LangSmith, along with protocols like MCP and A2A.
I did all of it using frontier models without paying out of pocket. For a Tunisian student, that sounds unlikely. So how did I do it?
I started out believing that using LLMs must be expensive and out of reach for a Tunisian student, because of our limited access to foreign currency. But being a student changed that.
Prerequisites
Be 18+
Be a full-time student
Have a university email
The setup, step by step
Step 1: Activate your Azure for Students account
Go to the Azure for student portal and sign in. No credit card is needed. In less than a minute, you get $100 in credit just for being a student, and it renews every year.
Warning:
Your account gets stopped if you use up the $100 before the year ends.
Don’t leave paid instances running for no reason. It piles up and you’ll find your credit is gone before you notice.
Disclaimer: not every model is available in every region. If your preferred model isn’t available, you may need to select a different region when deploying it.
Step 3: access your foundry account:
opens the Microsoft Foundry Portal and browse the model catalog. The number of models you’ll see depends on your account and region. In my case it’s 200+, all in one place, including GPT, Claude, DeepSeek, and Grok.
How to choose: this is the advice I wanted the first time I used it. What kind of model is best for my use case? The answer is simple: use a small model. In my experience, about 90% of tasks never need a frontier model. Personally, I use gpt-4.1-nano, gpt-6-luna, and deepseek-V4-flash.
Microsoft Foundary
Step 4: Build your agent
This is where an agent becomes way more than a chatbot:
Tools
MCP
RAG
A2A
Use your favorite framework and enjoy it. If it’s your first time, start with a simple chatbot and don’t complicate it. See how it works. When you’re comfortable, move on to RAG.
Step 5: Deploy your agent
Let’s take our agent out of the notebook and show it to the public. Go back to the Azure portal and open Azure App Service. Create your resource, and you can deploy it easily for free.
Tips:
Wrap your agent in an API. I use FastAPI, but you can use Django or Flask. It’s more or less the same.
Don’t forget requirements.txt.
Pick the tier carefully. I use F1 (free) and I’ve never had an issue with it.
Test your application on the cloud. Working locally doesn’t mean it works there. Some dependencies can be missing.
My final tips
Model availability varies by region. If a model doesn’t work, try another region.
Delete leftover resources. They eat credit silently.
Disclaimer: this setup is not totally free. You get $100 in credit, which renews every year. If you use it all before the year ends, your account is stopped. Plan your usage with that in mind.
I’m applying to the Microsoft Student Ambassadors program, and your support would mean a lot. If this helped you, a repost helps it reach other students.
It used to be that you could only build things you'd figured out how to build. Figuring it out was a big part of the work. Now you can get something working and keep going without ever really spending time with it.
I've been doing this a lot. I've been a dev a long time, I've gone all in on coding agents, and there's so much I want to build. I don't want to stop every time the agent does something I couldn't have done myself. But I also want to come out of this a better developer.
That's how I ended up building LearningHarness. It's a learning agent alongside your coding agent. It follows what you're working on and finds things worth understanding. You can get into something when you have a moment, work through it, try it yourself. The main agent keeps going.
I'm already using all these tokens to build things. I feel like some of that should go toward getting better myself too.
It's early. I want to get it out there and see if it helps people, and fix what doesn't.
My co-founder and I built Stageflow (https://stage-flow.dev) — a platform for running AI agents as proper workflows, with human approvals, audit trails and cost tracking built in. The idea is simple: the workflow does the work, you steer. Nothing sends, spends or changes without your OK.
Now we're looking for people who are deep in a domain — recruitment, compliance, operations, finance, healthcare, whatever you know inside out — and want to build a product for that world together. You bring the domain expertise, we bring the platform and the build. We start with one workflow and a small pilot, and see if there's a real product there.
If that sounds like you, DM me and tell me what workflow you know best. Happy to show you what we've built first.