@rudderhq/agent-runtime-gemini-local 0.1.0 → 0.2.0-canary.1
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@rudderhq/agent-runtime-gemini-local",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0-canary.1",
|
|
4
4
|
"license": "SEE LICENSE IN LICENSE",
|
|
5
5
|
"homepage": "https://github.com/Undertone0809/rudder",
|
|
6
6
|
"bugs": {
|
|
@@ -51,7 +51,7 @@
|
|
|
51
51
|
"typecheck": "tsc --noEmit"
|
|
52
52
|
},
|
|
53
53
|
"dependencies": {
|
|
54
|
-
"@rudderhq/agent-runtime-utils": "0.
|
|
54
|
+
"@rudderhq/agent-runtime-utils": "0.2.0-canary.1",
|
|
55
55
|
"picocolors": "^1.1.1"
|
|
56
56
|
},
|
|
57
57
|
"devDependencies": {
|
|
@@ -91,6 +91,11 @@ Required thinking:
|
|
|
91
91
|
- structured role/persona instructions for the new agent (`promptTemplate` when the CLI payload is the available surface; Rudder materializes this as `SOUL.md`)
|
|
92
92
|
- source issue linkage (`sourceIssueId` or `sourceIssueIds`) when this hire came from an issue
|
|
93
93
|
|
|
94
|
+
`role` is a fixed Rudder enum, not a free-form job title. Use one of:
|
|
95
|
+
`ceo`, `cto`, `cmo`, `cfo`, `engineer`, `designer`, `pm`, `qa`, `devops`, `researcher`, `general`.
|
|
96
|
+
Put specialization in `title`, `capabilities`, and `promptTemplate`. For example, a Founding Engineer hire should use
|
|
97
|
+
`"role": "engineer"` and `"title": "Founding Engineer"`, not `"role": "founding_engineer"`.
|
|
98
|
+
|
|
94
99
|
Do not copy Rudder's shared filesystem, memory, language, or safety contract into the hire prompt. Rudder injects that operating contract from runtime code for supported local runtimes. The hire-specific prompt should only define the new agent's role, identity, scope, tone, and durable responsibilities.
|
|
95
100
|
|
|
96
101
|
Draft `promptTemplate` as a durable SOUL document, not a one-line command. Use these sections when the role is not trivial:
|
|
@@ -106,6 +106,9 @@ Request body:
|
|
|
106
106
|
}
|
|
107
107
|
```
|
|
108
108
|
|
|
109
|
+
`role` is validated as a fixed enum: `ceo`, `cto`, `cmo`, `cfo`, `engineer`, `designer`, `pm`, `qa`, `devops`, `researcher`, `general`.
|
|
110
|
+
Use `title`, `capabilities`, and `agentRuntimeConfig.promptTemplate` for narrower job titles. For example, a Founding Engineer should be submitted as `"role": "engineer"` and `"title": "Founding Engineer"`.
|
|
111
|
+
|
|
109
112
|
Response when approval is required:
|
|
110
113
|
|
|
111
114
|
```json
|
|
@@ -102,7 +102,7 @@ Notes:
|
|
|
102
102
|
The `agent hire` payload accepts the same shape as the hire API, including:
|
|
103
103
|
|
|
104
104
|
- `name` optional; blank or omitted means Rudder assigns a distinct first name
|
|
105
|
-
- `role`
|
|
105
|
+
- `role`: one of `ceo`, `cto`, `cmo`, `cfo`, `engineer`, `designer`, `pm`, `qa`, `devops`, `researcher`, `general`
|
|
106
106
|
- `title`
|
|
107
107
|
- `icon`
|
|
108
108
|
- `reportsTo`
|
|
@@ -116,6 +116,8 @@ The `agent hire` payload accepts the same shape as the hire API, including:
|
|
|
116
116
|
- `sourceIssueId`
|
|
117
117
|
- `sourceIssueIds`
|
|
118
118
|
|
|
119
|
+
`role` is a fixed enum. Do not invent role keys such as `founding_engineer`, `frontend_engineer`, or `reviewer`. Use the closest enum value, then put the specialization in `title`, `capabilities`, and `agentRuntimeConfig.promptTemplate`; for example use `"role": "engineer"` with `"title": "Founding Engineer"`.
|
|
120
|
+
|
|
119
121
|
Issue linkage rule:
|
|
120
122
|
|
|
121
123
|
- prefer `sourceIssueId` or `sourceIssueIds` inside the hire payload
|