You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-25Lines changed: 7 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Go users can also install from source:
44
44
go install github.com/snowztech/vikusha/cmd/vikusha@latest
45
45
```
46
46
47
-
### Option 1: YAML
47
+
### Character YAML
48
48
49
49
Create `character.yaml`.
50
50
@@ -77,38 +77,20 @@ For structured turn logs, pass `-log-json`. Named agents append logs to `~/.viku
77
77
vikusha chat -log-json writer
78
78
```
79
79
80
-
You can load the same YAML from Go.
80
+
You can load the same character from Go.
81
81
82
82
```go
83
-
a, err:= vikusha.LoadAgent("character.yaml", vikusha.Options{})
83
+
a, err:= vikusha.LoadAgent("character.yaml", vikusha.BuildOptions{})
84
84
reply, err:= a.Chat(ctx, "lucas", "hello")
85
85
_ = reply
86
86
87
87
// From another goroutine or transport command:
88
88
a.Cancel("lucas")
89
89
```
90
90
91
-
### Option 2: Go
91
+
For advanced Go usage where you want to wire provider instances, tool registries, or memory yourself, use `agent.New`; see [examples/file_read](examples/file_read).
92
92
93
-
Use `agent.New` when you want to pass the provider and tools yourself.
The framework path is explicit Go construction: the caller passes providers, tools, and memory. The runtime path starts from YAML and lets Vikusha wire those pieces. Both paths produce the same `Agent` runtime.
36
+
The primary path is character-first: YAML describes the assistant, and Vikusha wires providers, tools, memory, workspace, and logging. The lower-level `agent.New`path remains available for advanced Go users who want to pass runtime dependencies themselves.
0 commit comments