create-loopengine 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 +29 -3
- package/package.json +1 -1
- package/template/package.json +1 -1
package/README.md
CHANGED
|
@@ -26,6 +26,12 @@ curl -X POST localhost:8787/agents/example-agent/messages \
|
|
|
26
26
|
-d '{"sessionId":"s1","message":"what is the weather in Boston?"}'
|
|
27
27
|
```
|
|
28
28
|
|
|
29
|
+
Or from the command line directly, no server needed:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
npm run cli -- --agent example-agent "what is the weather in Boston?"
|
|
33
|
+
```
|
|
34
|
+
|
|
29
35
|
No name given? `npm create loopengine@latest` on its own scaffolds into
|
|
30
36
|
`./my-agents`.
|
|
31
37
|
|
|
@@ -46,11 +52,31 @@ adapters/cli.ts Command-line adapter
|
|
|
46
52
|
The registry is multi-agent-capable from the start — seeded with one
|
|
47
53
|
example agent, not architecturally limited to one — so adding a second
|
|
48
54
|
agent later is one file plus one line in `agent-registry.ts`, not a
|
|
49
|
-
rewrite. See
|
|
50
|
-
|
|
51
|
-
full `AgentConfig` surface: permission rules, skills, context-budget
|
|
55
|
+
rewrite. See [loopengine's own README](https://github.com/evanyan22/loopengine)
|
|
56
|
+
for the full `AgentConfig` surface: permission rules, skills, context-budget
|
|
52
57
|
recovery, and how to wire a real model (Anthropic or OpenAI, both included).
|
|
53
58
|
|
|
59
|
+
## Add another agent
|
|
60
|
+
|
|
61
|
+
1. Copy `agents/example-agent.ts` to `agents/your-agent.ts` and edit its
|
|
62
|
+
`systemPrompt`, `tools`, and `rules`.
|
|
63
|
+
2. Register it in `agent-registry.ts` — one line, same shape as
|
|
64
|
+
`example-agent`.
|
|
65
|
+
3. Call it at `/agents/your-agent/messages`.
|
|
66
|
+
|
|
67
|
+
## Adding external tools via Composio
|
|
68
|
+
|
|
69
|
+
Need an agent to call a real SaaS action (list GitHub repos, send a Slack
|
|
70
|
+
message) instead of a hand-written tool? Route it through
|
|
71
|
+
[Composio](https://composio.dev) via
|
|
72
|
+
[`mcpplug`](https://www.npmjs.com/package/mcpplug) rather than owning that
|
|
73
|
+
vendor's OAuth yourself — see loopengine's own
|
|
74
|
+
[README section on external tool gateways](https://github.com/evanyan22/loopengine#external-tool-gateways)
|
|
75
|
+
for the pattern, and `agents/file-agent.ts` in that repo for a complete,
|
|
76
|
+
working example. Not wired in here by default: it needs the `composio` CLI
|
|
77
|
+
installed and an authenticated account (`composio link <toolkit>`) first,
|
|
78
|
+
so it's a deliberate next step, not part of this starter agent.
|
|
79
|
+
|
|
54
80
|
## Status
|
|
55
81
|
|
|
56
82
|
Verified end to end against the real published packages: `npm create
|
package/package.json
CHANGED