okiro 0.1.1 → 0.1.3
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.
- package/README.md +66 -37
- package/package.json +2 -3
package/README.md
CHANGED
|
@@ -1,6 +1,20 @@
|
|
|
1
1
|
# okiro
|
|
2
|
+
起きろ
|
|
2
3
|
|
|
3
|
-
|
|
4
|
+
Spawn ephemeral, parallel variations of your codebase. Let multiple AI agents tackle the same task, compare results, promote the best.
|
|
5
|
+
|
|
6
|
+
## Why?
|
|
7
|
+
|
|
8
|
+
AI agents don’t always get it right the first time.
|
|
9
|
+
okiro lets you see multiple real implementations before choosing which one belongs in your codebase.
|
|
10
|
+
|
|
11
|
+
## What is this exactly?
|
|
12
|
+
|
|
13
|
+
okiro does not run AI agents for you.
|
|
14
|
+
|
|
15
|
+
It creates isolated workspaces so tools like Cursor, Claude, Codex, or any other agent can work independently in parallel without touching your main codebase.
|
|
16
|
+
|
|
17
|
+
Think of it as cheap, disposable branches that are easy to diff and easy to throw away.
|
|
4
18
|
|
|
5
19
|
## Install
|
|
6
20
|
|
|
@@ -10,58 +24,73 @@ npm install -g okiro
|
|
|
10
24
|
|
|
11
25
|
## Usage
|
|
12
26
|
|
|
27
|
+
### Create variations
|
|
28
|
+
|
|
13
29
|
```bash
|
|
14
|
-
okiro 3
|
|
15
|
-
okiro 3 --prompt
|
|
16
|
-
okiro
|
|
17
|
-
okiro compare # Visual diff viewer
|
|
18
|
-
okiro promote var-2 # Apply winning variation
|
|
19
|
-
okiro cleanup # Remove all variations
|
|
30
|
+
okiro 3 # Create 3 copies of your codebase
|
|
31
|
+
okiro 3 --prompt # Create 3, prompt for direction per variation
|
|
32
|
+
okiro 3 --prompt "add dark mode" # Base task + per-variation directions
|
|
20
33
|
```
|
|
21
34
|
|
|
22
|
-
|
|
35
|
+
When using `--prompt`, okiro writes instructions to `AGENTS.md` and `.cursor/rules` so AI agents in each workspace know their specific approach.
|
|
36
|
+
|
|
37
|
+
### Compare changes
|
|
23
38
|
|
|
39
|
+
```bash
|
|
40
|
+
okiro compare # Open diff viewer in browser
|
|
41
|
+
okiro diff var-1 # CLI diff: original vs var-1
|
|
42
|
+
okiro diff var-1 var-2 # CLI diff: var-1 vs var-2
|
|
24
43
|
```
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
44
|
+
|
|
45
|
+
### Pick a winner
|
|
46
|
+
|
|
47
|
+
```bash
|
|
48
|
+
okiro promote var-2 # Apply var-2's changes to original
|
|
49
|
+
okiro promote var-2 -c # Promote and git commit
|
|
50
|
+
okiro promote var-2 -c "feat: dark mode using Tailwind"
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
### Cleanup
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
okiro status # Show active variations
|
|
57
|
+
okiro cleanup # Remove all variation workspaces
|
|
31
58
|
```
|
|
32
59
|
|
|
33
|
-
|
|
60
|
+
## How it works
|
|
34
61
|
|
|
35
|
-
|
|
62
|
+
1. **Efficient cloning** — Uses APFS clones on macOS and btrfs reflinks on Linux for instant, space-efficient copies. Falls back to rsync elsewhere.
|
|
36
63
|
|
|
37
|
-
|
|
64
|
+
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.
|
|
38
65
|
|
|
39
|
-
|
|
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 |
|
|
66
|
+
3. **Smart diffing** — Only tracks meaningful changes, ignoring `node_modules`, `.git`, `dist`, etc.
|
|
48
67
|
|
|
49
|
-
|
|
68
|
+
4. **Non-destructive** — Your original codebase is never touched until you explicitly `promote`.
|
|
50
69
|
|
|
51
|
-
|
|
70
|
+
## Example workflow
|
|
52
71
|
|
|
53
72
|
```bash
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
#
|
|
59
|
-
|
|
73
|
+
# You want to add authentication but aren't sure about the approach
|
|
74
|
+
cd my-app
|
|
75
|
+
okiro 3 --prompt "add user authentication"
|
|
76
|
+
|
|
77
|
+
# Enter directions when prompted:
|
|
78
|
+
# var-1: use Better Auth
|
|
79
|
+
# var-2: use Clerk
|
|
80
|
+
# var-3: roll our own with JWT + cookies
|
|
81
|
+
|
|
82
|
+
# Open each variation in a separate Cursor window
|
|
83
|
+
# Let the AI agents cook...
|
|
60
84
|
|
|
61
|
-
|
|
85
|
+
# Compare results
|
|
86
|
+
okiro compare
|
|
62
87
|
|
|
63
|
-
-
|
|
64
|
-
-
|
|
88
|
+
# var-1 looks cleanest, promote it
|
|
89
|
+
okiro promote var-1 -c "feat: add auth via Better Auth"
|
|
90
|
+
|
|
91
|
+
# Clean up
|
|
92
|
+
okiro cleanup
|
|
93
|
+
```
|
|
65
94
|
|
|
66
95
|
## License
|
|
67
96
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "okiro",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.1.3",
|
|
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",
|