Credit Guide
Understand your Kolega Studio credits
Last updated 7 months ago
π― Understanding Credits
Credits are the currency of Kolega Studio. Every interaction with the agents consumes credits, enabling you to build applications through natural conversation.
What Are Credits?
Credits = Kolega Studio Processing Power - Each credit represents computational resources
Pay-As-You-Build Model - You only use credits when actively developing
Transparent Usage - You can always see your remaining balance
Monthly Refresh - Credits reset with your subscription cycle
Purchase Credits - Credits can be topped up with any active subcription
π³ Subscription Tiers
Creator Plan - $20/month
Credits: 2,000 per month
Best for:
Individual developers
Learning the platform
Small projects
Prototypes and MVPs
Infrastructure Access:
Full Stack Web App template only
React + Vite + TypeScript frontend
Hono backend with MongoDB
Tailwind CSS and shadcn/ui built-in
Embedded GitLab auto repo for version control
Pro Plan - $59/month
Credits: 5,900 per month
Best for:
Professional developers
Agencies
Multiple projects
Complex applications
Infrastructure Options:
Full Web App - Same as Creator tier
Mobile App - React Native for iOS/Android (requires Expo Go setup)
Build from Scratch - Full flexibility without pre-built infrastructure
Additional Features:
Deployment to custom domains
GitHub integration (BYO repository)
Mobile app development with Expo Go
More infrastructure templates
Advanced agent capabilities
π‘ Credit Optimization Strategies
1. Use Threads Wisely
Inefficient:
One long thread for entire project
Context window fills up quickly
Higher credit usage per request
Efficient:
New thread per feature/phase
Clear task separation
Lower credit consumption
2. Create an Implementation Plan
Before building:
Use a separate thread for planning
Create detailed implementation checklist
Save as .md file in project
Reference plan in new threads
Benefits:
Reduces back-and-forth iterations
Agents have clear instructions
3. Be Specific in Requests
Inefficient:
"Make it better" "Add more features" "Fix the issues" Efficient:
"Create a task management app with:
- Task CRUD operations
- Priority levels (high/medium/low)
- Due dates
- Filter by status
- Modern UI with Tailwind CSS" 4. Batch Related Changes
Instead of:
"Add a header"
"Add a footer"
"Add navigation"
Do this: "Add a header with logo and navigation, and a footer with links and copyright"
5. Test Before Making Changes
Credit-saving workflow:
Complete a phase/feature
Test thoroughly in Preview
Make a list of ALL needed changes
Submit them together in one request
Save credits on iterations
π Managing Your Credits
Check Your Balance
Where to look:
Click your username (top right)
Navigate to Account β Credits
See remaining balance
View usage history
Check reset date
What you'll see:
Current balance (e.g., "1,938 credits remaining")
π¨ Credit Warnings & Limits
Context Window Warnings
When you see context window warnings:
Start a new thread immediately
Reference the implementation plan
Brief the new thread on completed work
Continue without losing context
What Happens at Zero Credits?
When credits are exhausted:
You can purchase additional credits within any active plan
Cannot make new AI requests
Existing projects remain accessible
Can still use Preview, publish, and export
Can download project ZIP
Credits refresh on billing date
Emergency Strategies
If running low on credits:
Purchase additional credits - You need an active subscription first
Prioritize critical features - Complete must-haves first
Download your project - Continue locally if needed
Wait for refresh - Credits reset monthly
Configure auto Top-Ups - Credits will automatically top up when a minimum set threshold is reached
Upgrade plan - Immediate access to more credits and features
Use existing code - Edit directly in Code Viewer
π Credit FAQ
Q: Do credits roll over? A: No, credits refresh monthly with your subscription.
Q: Can I buy additional credits? A: Yes, you can always buy additional credits.
Q: Do all actions use credits? A: Only AI interactions consume credits. Viewing, publishing, exporting are free.
Q: How can I reduce credit usage? A: Use multiple threads, create implementation plans, be specific in requests.
β Credit Best Practices Checklist
[ ] Check credit balance before starting large projects
[ ] Create an implementation plan before coding
[ ] Use separate threads for different features/phases
[ ] Write detailed, specific requests
[ ] Batch related changes together
[ ] Test thoroughly before requesting changes
[ ] Monitor context window warnings
[ ] Download projects regularly for backup
[ ] Track usage patterns
[ ] Upgrade plan if consistently running low
π―
Pro Tip: The key to credit efficiency is clear communication and smart thread management. The better you describe what you want and the more organized your threads, the fewer credits you'll use to achieve it.