Jev + Claude OS Setup Guide
Want help applying this to your idea? Tell me what you are trying to build and where you are stuck.
Send an emailStill sitting in front of your terminal typing prompts one by one like it's 2023? Bhai, you are working as the bottleneck in your own business. When you combine Jev — the open-source agent orchestrator — with a structured Claude OS environment, you turn Claude Code into an autonomous development factory. Instead of hand-holding every function call, you define the objective, set acceptance criteria, and let the system research, code, test, and self-correct on autopilot. Here is the complete end-to-end setup guide.
1. Why Traditional Chat Prompts Are Killing Your Productivity
Let's be completely honest about how most developers work with AI today: You open Claude Code, type a prompt, wait 45 seconds, review the code, find a small bug, explain the bug, wait again, copy the output, test it, and repeat. You are essentially acting as an unpaid human router between the AI and your code editor.
Jev flips this model completely on its head. It acts as an autonomous runtime layer that sits above Claude Code. Jev reads your project specification, breaks it down into a dependency graph of sub-tasks, assigns each sub-task to a specialized subagent, and doesn't ping you until the entire suite of automated tests passes. That is the true meaning of an Agentic OS.
2. The Claude OS Architecture: Memory, Skills, and Orchestration
To make Jev work effectively, your workspace needs three foundational pillars:
1. **Context & Memory Layer (`/context`)**: Markdown files defining who you are, your tech stack rules, API secrets schema, and brand guidelines so the agent never asks basic setup questions.
2. **Skills Repository (`/skills`)**: Modular instruction sets that teach the AI how to execute specific jobs — like Figma-to-Tailwind conversion, SEO auditing, or REST API endpoint creation.
3. **Jev Orchestration Engine**: The autonomous driver that reads your `PLAN.md`, spawns worker subagents, monitors progress, and manages state rollbacks if a task fails.
# Step 1: Create your structured workspace directory
mkdir -p ~/MyAgency-OS/{context,skills,projects,logs}
cd ~/MyAgency-OS
# Step 2: Clone Jev and install dependencies
git clone https://github.com/jev-ai/jev.git orchestrator
cd orchestrator && npm install
# Step 3: Install core skills globally into Claude Code
npx -y skills add anthropics/skills@frontend-design -g -y
npx -y skills add OthmanAdi/planning-with-files -g -y
npx -y skills add obra/superpowers -g -y3. Step-by-Step Configuration: From Zero to First Autonomous Run
Once the files are laid out, configure your `.env` file with your Anthropic API key and enable local filesystem tools. Here is how you trigger your first autonomous pipeline inside your terminal:
# Launch Jev with a client project specification
npx jev run --spec ./projects/client-d2c-store/SPEC.md \
--skills ./skills \
--auto-verify \
--max-iterations 15
# What Jev does automatically:
# 1. Spawns Scout Agent -> parses SPEC.md and audits existing components
# 2. Spawns Architect Agent -> writes docs/PLAN.md with verifiable checklists
# 3. Spawns Builder Agent -> implements code in discrete commits
# 4. Spawns Critic Agent -> executes npm run build & lint, fixing any errors4. Real Indian Agency Playbook: Automated Content & Client Onboarding
How are Indian founders monetizing this right now? Here are two battle-tested use cases delivering real client revenue:
**Use Case A: The Automated Web App Slicer (₹40K - ₹80K per project)**: Clients upload their Figma design links. Jev triggers a headless browser to inspect design tokens, generates matching Tailwind CSS components, wires the state, and deploys a live preview link to Vercel within 90 minutes with zero manual coding.
**Use Case B: The 24/7 Content Repurposing Factory**: Point Jev at your YouTube video link. It downloads the audio, extracts high-retention segments using transcript timestamps, writes 5 LinkedIn carousel drafts, creates Twitter threads, and stages them directly in your CMS.
5. Extracted Links & Developer Repositories
All official tools and repositories required to replicate this exact setup:
Jev AI Orchestrator Repository
Open-source agent orchestration harness designed for Claude Code and autonomous multi-agent pipelines.
GitHub: github.com/jev-ai/jev
Planning with Files (13,400+ Stars)
Persistent markdown task state tracking so autonomous agents never lose context across multi-hour runs.
GitHub: github.com/OthmanAdi/planning-with-files
npx -y skills add OthmanAdi/planning-with-files -g -yAnthropic Official Skills Collection
Curated skills for design, coding, and web artifact generation directly from Anthropic's engineering team.
GitHub: github.com/anthropics/skills
Ready to build something useful?
Use this guide as a starting point, then test your setup on one real task. If you want help finding a use case or building an AI agent, send me your problem statement.