Build your own personal AI agent using ElizaOS and deploy it on the Nosana decentralized compute network. Win a share of $3,000 USDC in prizes.
Inspired by OpenClaw — the self-hosted personal AI movement — this challenge is about giving AI back to the individual. Build an agent that runs on your own infrastructure, handles your own tasks, and keeps your own data.
Theme: Personal AI Agents — Build an AI agent that acts as a personal assistant, automate your life, or solve a real problem for yourself or your community. The use case is entirely up to you.
Framework: ElizaOS (latest v2) Compute: Nosana decentralized GPU network Model: Qwen3.5-27B (hosted endpoint provided by Nosana)
| Place | Prize |
|---|---|
| 🥇 1st | $1,000 USDC |
| 🥈 2nd | $750 USDC |
| 🥉 3rd | $450 USDC |
| 4th | $200 USDC |
| 5th–10th | $100 USDC each |
Follow Nosana's Luma for more information: Nosana Luma
There are no strict requirements on use case — build whatever is most useful to you. Some ideas to get started:
- 🗂️ Personal assistant — calendar, tasks, email drafting, reminders
- 🔍 Research agent — web search, summarization, knowledge synthesis
- 📱 Social media manager — Twitter/X, Telegram, Discord automation
- 💰 DeFi/crypto agent — portfolio monitoring, on-chain alerts, trading insights
- 🏠 Home automation — smart home control, IoT integration
- 🛠️ DevOps helper — monitor services, automate deployments
- 🎨 Content creator — blog posts, social copy, creative writing
Tip: ElizaOS has a rich plugin ecosystem. Explore existing plugins and templates before building from scratch — you might find 80% of what you need already exists.
- Node.js 23+
- pnpm (
npm install -g pnpm) - Docker (for deployment)
- Git
# Fork this repo, then clone your fork
git clone https://github.com/YOUR-USERNAME/agent-challenge
cd agent-challenge
# Copy and configure environment variables
cp .env.example .env
# Edit .env with your Nosana endpoint details
# Install dependencies
bun i -g @elizaos/cli
# Start your agent in development mode
elizaos devOpen http://localhost:3000 to see the ElizaOS built-in client.
All challenge participants get free compute credits to deploy and run their agents on Nosana.
How to claim:
- Visit nosana.com/builders-credits
- Sign up or log in with your wallet
- Your credits will be added to your account automatically
- Use these credits to deploy your ElizaOS agent to the Nosana network
These credits cover the compute costs for running your agent during the challenge period.
Note: Credits are airdropped twice a day. Please be patient if you don't see them immediately after signing up.
Nosana provides a hosted Qwen3.5-27B-AWQ-4bit endpoint for challenge participants. Update your .env:
OPENAI_API_KEY=nosana
OPENAI_API_URL=https://6vq2bcqphcansrs9b88ztxfs88oqy7etah2ugudytv2x.node.k8s.prd.nos.ci/v1
MODEL_NAME=Qwen3.5-27B-AWQ-4bitModel Details:
- Model ID:
Qwen3.5-27B-AWQ-4bit - Max Context Length: 60,000 tokens
- Provider: Nosana decentralized inference
- Base Model: cyankiwi/Qwen3.5-27B-AWQ-4bit
ollama pull qwen3.5:27b # or a smaller one for your system
ollama serveOPENAI_API_KEY=ollama
OPENAI_API_URL=http://127.0.0.1:11434/v1
MODEL_NAME=qwen3.5:27bEdit characters/agent.character.json to define your agent's personality, knowledge, and behavior:
{
"name": "MyAgent",
"bio": ["Your agent's backstory and capabilities"],
"system": "Your agent's core instructions and behavior",
"plugins": ["@elizaos/plugin-bootstrap", "@elizaos/plugin-openai"],
"clients": ["direct"]
}Extend your agent by adding plugins to package.json and your character file:
| Plugin | Use Case |
|---|---|
@elizaos/plugin-bootstrap |
Required base plugin |
@elizaos/plugin-openai |
OpenAI-compatible LLM (required for Nosana endpoint) |
@elizaos/plugin-web-search |
Web search capability |
@elizaos/plugin-telegram |
Telegram bot client |
@elizaos/plugin-discord |
Discord bot client |
@elizaos/plugin-twitter |
Twitter/X integration |
@elizaos/plugin-browser |
Browser/web automation |
@elizaos/plugin-sql |
Database access |
Install a plugin:
pnpm add @elizaos/plugin-web-searchAdd it to your character file:
{
"plugins": ["@elizaos/plugin-bootstrap", "@elizaos/plugin-openai", "@elizaos/plugin-web-search"]
}Add your own custom logic in src/index.ts. See the example plugin already included.
SQLite is configured by default — sufficient for development and small-scale agents. For a production-grade personal agent, consider:
- A mounted volume on Nosana
- External database (PostgreSQL, PlanetScale, etc.)
- Decentralized storage (Arweave, IPFS)
Important: For this challenge, you must deploy your agent to Nosana's decentralized infrastructure. Do not use the standard
elizaos deploycommand — that deploys to centralized cloud providers. This challenge is about embracing decentralized compute.
Why Nosana?
- Decentralized — Your agent runs on a distributed network of GPU providers, not AWS/GCP/Azure
- Cost-effective — Use your free builders credits (no credit card required)
- Permissionless — No vendor lock-in, full control over your infrastructure
- Challenge requirement — All submissions must be deployed on Nosana
Before deploying, ensure you have:
- Docker installed and running
- A Docker Hub account (free)
- Your Nosana builders credits claimed
Your agent needs to be containerized and available on a public registry (Docker Hub) so Nosana nodes can pull and run it.
# Build your Docker image
docker build -t yourusername/nosana-eliza-agent:latest .
# Test it locally first (recommended)
docker run -p 3000:3000 --env-file .env yourusername/nosana-eliza-agent:latest
# Visit http://localhost:3000 to verify it works
# Log in to Docker Hub
docker login
# Push to Docker Hub (make it public)
docker push yourusername/nosana-eliza-agent:latestTip: Replace
yourusernamewith your actual Docker Hub username. Make sure your repository is public so Nosana nodes can pull it.
Edit nos_job_def/nosana_eliza_job_definition.json and update the Docker image reference:
{
"version": "0.1",
"type": "container",
"meta": {
"trigger": "cli"
},
"ops": [
{
"type": "container/run",
"id": "eliza-agent",
"args": {
"image": "yourusername/nosana-eliza-agent:latest", // <- Change this
"ports": ["3000:3000"],
"env": {
"OPENAI_API_KEY": "nosana",
"OPENAI_API_URL": "https://6vq2bcqphcansrs9b88ztxfs88oqy7etah2ugudytv2x.node.k8s.prd.nos.ci/v1",
"MODEL_NAME": "Qwen3.5-27B-AWQ-4bit"
}
}
}
]
}Security Note: For production deployments, avoid hardcoding sensitive environment variables. Consider using Nosana secrets management or external secret stores.
This is the recommended method for beginners:
- Visit the Nosana Dashboard
- Connect your Solana wallet (you need this for authentication and using credits)
- Click Expand to open the job definition editor
- Copy and paste the contents of your
nos_job_def/nosana_eliza_job_definition.jsonfile - Select your preferred compute market:
nvidia-3090— High performance (recommended for production)nvidia-rtx-4090— Premium performancecpu-only— Budget option (slower inference)
- Click Deploy
- Wait for a node to pick up your job (usually 30-60 seconds)
- Once running, you'll receive a public URL to access your agent
For developers who prefer the command line or want to automate deployments:
- First get your API key at https://deploy.nosana.com/account/
- Edit the Nosana ElizaOS Job Definition File
- Learn more about Nosana Job Definition Here
# Install the Nosana CLI globally
npm install -g @nosana/cli
# Deploy your agent
nosana job post \
--file ./nos_job_def/nosana_eliza_job_definition.json \
--market nvidia-4090 \
--timeout 300 \
--api <API_KEY>
# Monitor your deployment
nosana job status <job-id>
# View logs
nosana job logs <job-id>CLI Flags Explained:
--file— Path to your job definition JSON--market— Which GPU market to use (nvidia-3090, nvidia-rtx-4090, etc.)--timeout— Maximum job runtime in minutes
Once your job is running on Nosana:
- Test the endpoint — Visit the public URL provided by Nosana
- Check agent responsiveness — Send a test message to your agent
- Monitor logs — Use the Nosana Dashboard or CLI to view logs
- Verify inference — Ensure the Qwen3.5-27B model is responding correctly
Agent not starting?
- Check that your Docker image is public on Docker Hub
- Verify your job definition JSON is valid
- Ensure environment variables are correctly set
- Check Nosana dashboard logs for error messages
Slow response times?
- Consider using a higher-tier GPU market (nvidia-rtx-4090)
- Optimize your ElizaOS configuration
- Check if the Nosana inference endpoint is reachable
Out of credits?
- Visit nosana.com/builders-credits to check your balance
- Credits are airdropped twice daily — be patient if you just signed up
Need help?
- Join the Nosana Discord for support
- Check the Nosana documentation
- Review the Nosana CLI docs
Your submission should include:
- A working AI agent built with ElizaOS
- A frontend interface to interact with your agent (web UI, chat interface, dashboard, etc.)
- Deployment on Nosana — your agent must run on Nosana's decentralized infrastructure
The deeper your Nosana integration, the better your score. We're looking for projects that fully embrace decentralized infrastructure — not just a minimal deployment, but thoughtful integration into your architecture.
- Using Nosana for both training and inference
- Multi-node deployments across Nosana's network
- Custom deployment pipelines using Nosana CLI
- Monitoring and observability integrated with Nosana infrastructure
- Storage solutions that leverage decentralized networks
- Creative use of Nosana's compute marketplace
Submit your project via the official submission page: superteam.fun/earn/listing/nosana-builders-elizaos-challenge/ before April 14, 2026.
Submission Checklist — All items are required:
- Fork this repository and build your agent on the
elizaos-challengebranch - Build a frontend/UI for interacting with your agent
- Deploy to Nosana and get your public deployment URL (agent must run on Nosana infrastructure)
- Star the following repositories:
- Make a social media post about your project on your platform of choice (X/Twitter, LinkedIn, Bluesky, Instagram, or other)
- Provide your GitHub fork link (public repository)
- Provide your Nosana deployment URL (running agent)
- Write a description of your agent and what it does (≤300 words)
- Record a video demo (<1 minute) showing your agent and frontend in action
⚠️ Important: Submissions that do not meet these requirements will not be considered.
For complete submission requirements and additional information, visit the official challenge page.
| Criterion | Weight |
|---|---|
| Technical implementation | 25% |
| Nosana integration depth | 25% |
| Usefulness & UX | 25% |
| Creativity & originality | 15% |
| Documentation | 10% |
Judging Details:
- Technical implementation (25%) — Code quality, architecture, and ElizaOS best practices
- Nosana integration depth (25%) — How deeply Nosana is integrated into your deployment and infrastructure
- Usefulness & UX (25%) — Real-world applicability, frontend quality, and user experience
- Creativity & originality (15%) — Innovative use cases and novel approaches
- Documentation (10%) — Code quality, README, setup instructions
Judges: DevRel Lead & Ecosystem Specialist, Nosana
├── characters/
│ └── agent.character.json # Your agent's character definition
├── src/
│ └── index.ts # Custom plugin entry point (optional)
├── nos_job_def/
│ └── nosana_eliza_job_definition.json # Nosana deployment config
├── Dockerfile # Container configuration
├── .env.example # Environment variable template
└── package.json
- ElizaOS Documentation — Full framework docs
- ElizaOS Plugin Directory — Browse available plugins
- ElizaOS GitHub — Source code and examples
- ElizaOS Discord — Community support
- Nosana Documentation — Platform guide
- Nosana Dashboard — Deploy and manage jobs
- Nosana CLI — Command-line deployment
- Nosana Discord — Support and endpoint URL
- Discord — Join Nosana Discord for support, the Nosana endpoint URL, and to connect with other builders
- Twitter/X — Follow @nosana_ai and @elizaos for updates
- GitHub — Open an issue in this repo if you find problems with the template
This template is open source and available under the MIT License.
Built with ElizaOS · Deployed on Nosana · Powered by Qwen3.5

