okiro 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +57 -37
  2. package/package.json +2 -3
package/README.md CHANGED
@@ -1,6 +1,11 @@
1
1
  # okiro
2
+ 起きろ
2
3
 
3
- Sandboxed AI coding variations. Generate N approaches, compare diffs, promote the winner.
4
+ Spawn ephemeral, parallel variations of your codebase, let multiple AI agents tackle the same task with different approaches, then compare and promote the best one.
5
+
6
+ ## Why?
7
+
8
+ When you're unsure which approach is best: Tailwind vs custom tokens, TanStack vs lightweight fetch layer, or even different architectural patterns, you can have multiple AI agents work on isolated copies of your code simultaneously. Compare the results side-by-side, pick the winner, and merge it back.
4
9
 
5
10
  ## Install
6
11
 
@@ -10,58 +15,73 @@ npm install -g okiro
10
15
 
11
16
  ## Usage
12
17
 
18
+ ### Create variations
19
+
13
20
  ```bash
14
- okiro 3 # Create 3 sandboxed variations
15
- okiro 3 --prompt # With AI directions per variation
16
- okiro status # See what changed
17
- okiro compare # Visual diff viewer
18
- okiro promote var-2 # Apply winning variation
19
- okiro cleanup # Remove all variations
21
+ okiro 3 # Create 3 copies of your codebase
22
+ okiro 3 --prompt # Create 3, prompt for direction per variation
23
+ okiro 3 --prompt "add dark mode" # Base task + per-variation directions
20
24
  ```
21
25
 
22
- ## How it works
26
+ When using `--prompt`, okiro writes instructions to `AGENTS.md` and `.cursor/rules` so AI agents in each workspace know their specific approach.
27
+
28
+ ### Compare changes
23
29
 
30
+ ```bash
31
+ okiro compare # Open diff viewer in browser
32
+ okiro diff var-1 # CLI diff: original vs var-1
33
+ okiro diff var-1 var-2 # CLI diff: var-1 vs var-2
24
34
  ```
25
- Your Project Sandboxed Variations
26
- ──────────── ────────────────────
27
- /my-app/ ~/.okiro/projects/my-app/
28
- ├── src/ ├── var-1/ ← AI writes here
29
- └── ... ├── var-2/ ← AI writes here
30
- └── var-3/ ← AI writes here
35
+
36
+ ### Pick a winner
37
+
38
+ ```bash
39
+ okiro promote var-2 # Apply var-2's changes to original
40
+ okiro promote var-2 -c # Promote and git commit
41
+ okiro promote var-2 -c "feat: dark mode using Tailwind"
31
42
  ```
32
43
 
33
- Okiro clones your project using APFS copy-on-write (macOS) or reflinks (Linux). Clones are instant and use zero disk space until files change.
44
+ ### Cleanup
34
45
 
35
- Each AI session (Claude Code, Cursor, Opencode, etc.) works in its own sandbox without knowing it's sandboxed.
46
+ ```bash
47
+ okiro status # Show active variations
48
+ okiro cleanup # Remove all variation workspaces
49
+ ```
50
+
51
+ ## How it works
36
52
 
37
- ## Commands
53
+ 1. **Efficient cloning** — Uses APFS clones on macOS and btrfs reflinks on Linux for instant, space-efficient copies. Falls back to rsync elsewhere.
38
54
 
39
- | Command | Description |
40
- |---------|-------------|
41
- | `okiro <n>` | Create n variations, open terminals |
42
- | `okiro status` | Show variations and changed files |
43
- | `okiro diff var-1` | CLI diff against original |
44
- | `okiro compare` | Web diff viewer (split/unified, syntax highlighting) |
45
- | `okiro promote var-2` | Copy changes to your project |
46
- | `okiro promote var-2 --commit "msg"` | Promote and git commit |
47
- | `okiro cleanup` | Remove all variations |
55
+ 2. **Isolated workspaces** Each variation is a full copy at `~/.okiro/<project>/var-N/`. Open them in separate editor windows, run different agents, go wild.
48
56
 
49
- ## AI Integration
57
+ 3. **Smart diffing** — Only tracks meaningful changes, ignoring `node_modules`, `.git`, `dist`, etc.
50
58
 
51
- With `--prompt`, okiro creates `AGENTS.md` and `.cursor/rules` in each variation with your directions. The AI picks these up automatically.
59
+ 4. **Non-destructive** Your original codebase is never touched until you explicitly `promote`.
60
+
61
+ ## Example workflow
52
62
 
53
63
  ```bash
54
- okiro 3 --prompt "Refactor the auth module"
55
- # Then enter a direction for each variation:
56
- # var-1: Use JWT
57
- # var-2: Use sessions
58
- # var-3: Use OAuth
59
- ```
64
+ # You want to add authentication but aren't sure about the approach
65
+ cd my-app
66
+ okiro 3 --prompt "add user authentication"
60
67
 
61
- ## Requirements
68
+ # Enter directions when prompted:
69
+ # var-1: use Better Auth
70
+ # var-2: use Clerk
71
+ # var-3: roll our own with JWT + cookies
62
72
 
63
- - Node.js 18+
64
- - macOS 10.13+ or Linux
73
+ # Open each variation in a separate Cursor window
74
+ # Let the AI agents cook...
75
+
76
+ # Compare results
77
+ okiro compare
78
+
79
+ # var-1 looks cleanest, promote it
80
+ okiro promote var-1 -c "feat: add auth via Better Auth"
81
+
82
+ # Clean up
83
+ okiro cleanup
84
+ ```
65
85
 
66
86
  ## License
67
87
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "okiro",
3
- "version": "0.1.1",
4
- "description": "Ephemeral code variation previews for AI-assisted development",
3
+ "version": "0.1.2",
4
+ "description": "Spawn parallel AI coding variations, compare approaches, promote the winner",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "okiro": "./dist/index.js"
@@ -39,7 +39,6 @@
39
39
  "variations",
40
40
  "preview",
41
41
  "diff",
42
- "ephemeral",
43
42
  "cli",
44
43
  "claude",
45
44
  "cursor",