domino-agent 0.1.0__tar.gz

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.
@@ -0,0 +1,202 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
202
+
@@ -0,0 +1,4 @@
1
+ domino-agent
2
+ Copyright 2026 Domino Data Lab, Inc.
3
+
4
+ This product is licensed under the Apache License, Version 2.0. See the LICENSE file.
@@ -0,0 +1,185 @@
1
+ Metadata-Version: 2.4
2
+ Name: domino-agent
3
+ Version: 0.1.0
4
+ Summary: Register an agent folder in git with the Domino agent service: domino-agent deploy, and domino-agent pull.
5
+ License-Expression: Apache-2.0
6
+ Classifier: Development Status :: 4 - Beta
7
+ Classifier: Environment :: Console
8
+ Classifier: Intended Audience :: Developers
9
+ Classifier: Operating System :: POSIX
10
+ Classifier: Programming Language :: Python :: 3
11
+ Classifier: Programming Language :: Python :: 3 :: Only
12
+ Classifier: Programming Language :: Python :: 3.10
13
+ Classifier: Programming Language :: Python :: 3.11
14
+ Classifier: Programming Language :: Python :: 3.12
15
+ Classifier: Programming Language :: Python :: 3.13
16
+ Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
17
+ Classifier: Topic :: Software Development :: Libraries :: Python Modules
18
+ Requires-Python: >=3.10
19
+ Description-Content-Type: text/markdown
20
+ License-File: LICENSE
21
+ License-File: NOTICE
22
+ Requires-Dist: ruamel.yaml>=0.18
23
+ Dynamic: license-file
24
+
25
+ # domino-agent
26
+
27
+ `domino-agent` is the command for an agent folder on the Domino agent service. An agent folder is a folder in git that holds one
28
+ agent's definition. `domino-agent deploy` brings the folder into the agent service: that is a Registration, and the agent is then a
29
+ registered agent, whose definition has git as its source of truth. `domino-agent pull` writes the agent folder of an agent that
30
+ exists.
31
+
32
+ The agent service runs governed agents on Domino. You need its address and a Domino token: see "Sign in" below.
33
+
34
+ ## Install
35
+
36
+ ```
37
+ pip install domino-agent
38
+ ```
39
+
40
+ It needs Python 3.10 or later, and the `git` command. Each command has its help:
41
+
42
+ ```
43
+ domino-agent --version
44
+ domino-agent deploy --help
45
+ domino-agent pull --help
46
+ ```
47
+
48
+ ## A small agent folder
49
+
50
+ ```
51
+ governance-agent/ the agent folder
52
+ definition.md the definition file: the settings, and the instructions below them
53
+ instructions.md optional: the instructions in their own file, not below the settings
54
+ skills/
55
+ policy-evidence/ an own skill: only this agent has it
56
+ SKILL.md
57
+ subagents/
58
+ reviewer.md a custom subagent: a helper with its own instructions, and the agent's tools or fewer
59
+ ```
60
+
61
+ The definition file has its settings as YAML between two `---` lines, and the instructions below them:
62
+
63
+ ```markdown
64
+ ---
65
+ name: governance-agent # the identifier: lowercase letters, numbers and hyphens
66
+ title: Governance Agent # the name that people see
67
+ description: Investigates failing policy checks and writes findings.
68
+ model: [sonnet, haiku] # aliases of the LLM Gateway: the first one, then the fallback
69
+ ---
70
+ You are Domino's Governance Agent. You help bundle owners understand why a policy check failed.
71
+ ```
72
+
73
+ - `name`, `title` and `model` are required. A field that has its default value doesn't have to be in the file.
74
+ - A field that the command doesn't know is refused, with the list of the fields that it knows.
75
+ - `deploy` uploads only the known paths: `definition.md`, `instructions.md`, the files of `skills/<name>/`, and
76
+ `subagents/<file>.md`. Other files, such as a README, stay in git. The folders `tools/` and `schedules/` are refused: they are
77
+ kept for later.
78
+ - No secret goes in the folder. `deploy` refuses any text that looks like a credential.
79
+ - An own skill's `SKILL.md` has `name` (the folder's name) and `description` on top. A store skill of the agent service's skills
80
+ store goes in the definition file as `name@version`, such as `skills: [domino-governance-review@1.2.0]`.
81
+ - A custom subagent never has more than its agent: a tool, an access or a model that the agent doesn't have is refused.
82
+
83
+ ## Sign in
84
+
85
+ The command calls the agent service as you, with your Domino token. It reads three environment variables:
86
+
87
+ - `AGENT_SERVICE_URL`: the agent service's address, the URL of its Domino App. Always set it.
88
+ - `DOMINO_TOKEN`: your Domino token, such as a personal access token. Set it on a laptop or in a pipeline.
89
+ - `DOMINO_API_PROXY`: the token sidecar of a Domino workspace. Its default is `http://localhost:8899`, so you don't set it.
90
+
91
+ In a Domino workspace, set only the address. The command gets your token from the workspace for each request:
92
+
93
+ ```
94
+ export AGENT_SERVICE_URL=https://<domino host>/apps/<app id>
95
+ ```
96
+
97
+ On a laptop or in a pipeline, set your token too:
98
+
99
+ ```
100
+ export AGENT_SERVICE_URL=https://<domino host>/apps/<app id>
101
+ export DOMINO_TOKEN=<your Domino token>
102
+ ```
103
+
104
+ When the token is missing, expired or refused, the output starts with "Sign-in problem, not about the agent folder". A redirect or
105
+ a login page means that you are not signed in, or that Domino has no consent yet: open the App's URL once in a browser, then try
106
+ again.
107
+
108
+ ## deploy
109
+
110
+ `deploy` registers the agent folder at a path, or in the current folder. Commit the folder first:
111
+
112
+ ```
113
+ domino-agent deploy governance-agent --dry-run
114
+ domino-agent deploy governance-agent
115
+ ```
116
+
117
+ In this order, it:
118
+
119
+ 1. Checks the folder on your side, with no network call. Each refusal names the file, the line and a fix.
120
+ 2. Reads git: the repo's URL (with no credential in it), the branch, the folder's path in the repo, and the commit.
121
+ 3. Sends the known files with the commit. The agent service checks them again, then creates the agent, updates it, or says "No
122
+ change".
123
+
124
+ A new `name` makes a new agent that you own. A registered `name` updates that agent, when you can edit it and the folder is in the
125
+ recorded repo and path. The output:
126
+
127
+ ```
128
+ Created Governance Agent (agt_0123456789)
129
+ Page: https://agents.example.com/#/agents/agt_0123456789
130
+ Changed: title, description, model, instructions, skills/policy-evidence, subagents
131
+ Source: 3f2a9c1e7b4d on main, governance-agent in https://github.com/acme/agents.git
132
+ ```
133
+
134
+ A refusal:
135
+
136
+ ```
137
+ governance-agent/definition.md:6: `limits.minutes` must be a whole number from 1 to 480, not `900`. Fix: Write `limits.minutes: 1` or another number in that range
138
+ The agent folder was refused: 1 problem. Nothing was registered.
139
+ ```
140
+
141
+ The options:
142
+
143
+ - `--dry-run`: run every check, the agent service's too, and say what the deploy would do. Nothing is registered.
144
+ - `--allow-dirty`: for a test: register the folder with changes that are not committed, or outside a git repo. The agent's record
145
+ then says that it is not clean: `domino-agent deploy governance-agent --allow-dirty`
146
+ - `--branch NAME`: the branch to record when the checkout has none (a detached HEAD, as in a pipeline):
147
+ `domino-agent deploy governance-agent --branch main`
148
+ - `--move`: the agent's `name` is registered from another repo or path, and the move is intended. The agent's record gets this repo
149
+ and path: `domino-agent deploy governance-agent --move`
150
+
151
+ The exit code is 0 when the deploy is done, 1 when it is refused or fails (the output says why), and 2 for a wrong command line.
152
+
153
+ ## pull
154
+
155
+ `pull` writes the agent folder of an agent that you can edit. With no `--agent`, it lists the agents that you can edit, and you
156
+ select one by its number:
157
+
158
+ ```
159
+ domino-agent pull
160
+ ```
161
+
162
+ In a script, name the agent with its ID, or with a registered agent's `name`:
163
+
164
+ ```
165
+ domino-agent pull --agent agt_0123456789
166
+ domino-agent pull governance-agent --agent governance-agent
167
+ ```
168
+
169
+ - The folder's default path is a new folder named after the agent's `name`. Give a path to write it in another place.
170
+ - The definition file has an ID line, `id: <the agent's ID>`. Nobody types it. After a commit, `domino-agent deploy` of the folder
171
+ connects it to the same agent, which keeps its ID, its tasks and its history.
172
+ - A wizard agent (one made in the agent service's UI or with its API) moves to git this way: `pull` it, commit the folder, then
173
+ `deploy` it.
174
+ - `pull` refuses to write into a folder that has files. `--force` writes into it: the agent's files replace them, and each known
175
+ file that the agent doesn't have (`instructions.md`, a skill's file, a subagent file) is removed, so that an old one doesn't
176
+ deploy. Other files, such as a README, stay.
177
+ - `pull` refuses a framework agent: an agent folder holds only harness agents for now.
178
+
179
+ ## Changes
180
+
181
+ - 0.1.0: the first release. `deploy` and `pull`; the definition file; own skills, store skills and custom subagents.
182
+
183
+ ## License
184
+
185
+ Apache-2.0. Copyright 2026 Domino Data Lab, Inc. The LICENSE and NOTICE files are in the package.
@@ -0,0 +1,161 @@
1
+ # domino-agent
2
+
3
+ `domino-agent` is the command for an agent folder on the Domino agent service. An agent folder is a folder in git that holds one
4
+ agent's definition. `domino-agent deploy` brings the folder into the agent service: that is a Registration, and the agent is then a
5
+ registered agent, whose definition has git as its source of truth. `domino-agent pull` writes the agent folder of an agent that
6
+ exists.
7
+
8
+ The agent service runs governed agents on Domino. You need its address and a Domino token: see "Sign in" below.
9
+
10
+ ## Install
11
+
12
+ ```
13
+ pip install domino-agent
14
+ ```
15
+
16
+ It needs Python 3.10 or later, and the `git` command. Each command has its help:
17
+
18
+ ```
19
+ domino-agent --version
20
+ domino-agent deploy --help
21
+ domino-agent pull --help
22
+ ```
23
+
24
+ ## A small agent folder
25
+
26
+ ```
27
+ governance-agent/ the agent folder
28
+ definition.md the definition file: the settings, and the instructions below them
29
+ instructions.md optional: the instructions in their own file, not below the settings
30
+ skills/
31
+ policy-evidence/ an own skill: only this agent has it
32
+ SKILL.md
33
+ subagents/
34
+ reviewer.md a custom subagent: a helper with its own instructions, and the agent's tools or fewer
35
+ ```
36
+
37
+ The definition file has its settings as YAML between two `---` lines, and the instructions below them:
38
+
39
+ ```markdown
40
+ ---
41
+ name: governance-agent # the identifier: lowercase letters, numbers and hyphens
42
+ title: Governance Agent # the name that people see
43
+ description: Investigates failing policy checks and writes findings.
44
+ model: [sonnet, haiku] # aliases of the LLM Gateway: the first one, then the fallback
45
+ ---
46
+ You are Domino's Governance Agent. You help bundle owners understand why a policy check failed.
47
+ ```
48
+
49
+ - `name`, `title` and `model` are required. A field that has its default value doesn't have to be in the file.
50
+ - A field that the command doesn't know is refused, with the list of the fields that it knows.
51
+ - `deploy` uploads only the known paths: `definition.md`, `instructions.md`, the files of `skills/<name>/`, and
52
+ `subagents/<file>.md`. Other files, such as a README, stay in git. The folders `tools/` and `schedules/` are refused: they are
53
+ kept for later.
54
+ - No secret goes in the folder. `deploy` refuses any text that looks like a credential.
55
+ - An own skill's `SKILL.md` has `name` (the folder's name) and `description` on top. A store skill of the agent service's skills
56
+ store goes in the definition file as `name@version`, such as `skills: [domino-governance-review@1.2.0]`.
57
+ - A custom subagent never has more than its agent: a tool, an access or a model that the agent doesn't have is refused.
58
+
59
+ ## Sign in
60
+
61
+ The command calls the agent service as you, with your Domino token. It reads three environment variables:
62
+
63
+ - `AGENT_SERVICE_URL`: the agent service's address, the URL of its Domino App. Always set it.
64
+ - `DOMINO_TOKEN`: your Domino token, such as a personal access token. Set it on a laptop or in a pipeline.
65
+ - `DOMINO_API_PROXY`: the token sidecar of a Domino workspace. Its default is `http://localhost:8899`, so you don't set it.
66
+
67
+ In a Domino workspace, set only the address. The command gets your token from the workspace for each request:
68
+
69
+ ```
70
+ export AGENT_SERVICE_URL=https://<domino host>/apps/<app id>
71
+ ```
72
+
73
+ On a laptop or in a pipeline, set your token too:
74
+
75
+ ```
76
+ export AGENT_SERVICE_URL=https://<domino host>/apps/<app id>
77
+ export DOMINO_TOKEN=<your Domino token>
78
+ ```
79
+
80
+ When the token is missing, expired or refused, the output starts with "Sign-in problem, not about the agent folder". A redirect or
81
+ a login page means that you are not signed in, or that Domino has no consent yet: open the App's URL once in a browser, then try
82
+ again.
83
+
84
+ ## deploy
85
+
86
+ `deploy` registers the agent folder at a path, or in the current folder. Commit the folder first:
87
+
88
+ ```
89
+ domino-agent deploy governance-agent --dry-run
90
+ domino-agent deploy governance-agent
91
+ ```
92
+
93
+ In this order, it:
94
+
95
+ 1. Checks the folder on your side, with no network call. Each refusal names the file, the line and a fix.
96
+ 2. Reads git: the repo's URL (with no credential in it), the branch, the folder's path in the repo, and the commit.
97
+ 3. Sends the known files with the commit. The agent service checks them again, then creates the agent, updates it, or says "No
98
+ change".
99
+
100
+ A new `name` makes a new agent that you own. A registered `name` updates that agent, when you can edit it and the folder is in the
101
+ recorded repo and path. The output:
102
+
103
+ ```
104
+ Created Governance Agent (agt_0123456789)
105
+ Page: https://agents.example.com/#/agents/agt_0123456789
106
+ Changed: title, description, model, instructions, skills/policy-evidence, subagents
107
+ Source: 3f2a9c1e7b4d on main, governance-agent in https://github.com/acme/agents.git
108
+ ```
109
+
110
+ A refusal:
111
+
112
+ ```
113
+ governance-agent/definition.md:6: `limits.minutes` must be a whole number from 1 to 480, not `900`. Fix: Write `limits.minutes: 1` or another number in that range
114
+ The agent folder was refused: 1 problem. Nothing was registered.
115
+ ```
116
+
117
+ The options:
118
+
119
+ - `--dry-run`: run every check, the agent service's too, and say what the deploy would do. Nothing is registered.
120
+ - `--allow-dirty`: for a test: register the folder with changes that are not committed, or outside a git repo. The agent's record
121
+ then says that it is not clean: `domino-agent deploy governance-agent --allow-dirty`
122
+ - `--branch NAME`: the branch to record when the checkout has none (a detached HEAD, as in a pipeline):
123
+ `domino-agent deploy governance-agent --branch main`
124
+ - `--move`: the agent's `name` is registered from another repo or path, and the move is intended. The agent's record gets this repo
125
+ and path: `domino-agent deploy governance-agent --move`
126
+
127
+ The exit code is 0 when the deploy is done, 1 when it is refused or fails (the output says why), and 2 for a wrong command line.
128
+
129
+ ## pull
130
+
131
+ `pull` writes the agent folder of an agent that you can edit. With no `--agent`, it lists the agents that you can edit, and you
132
+ select one by its number:
133
+
134
+ ```
135
+ domino-agent pull
136
+ ```
137
+
138
+ In a script, name the agent with its ID, or with a registered agent's `name`:
139
+
140
+ ```
141
+ domino-agent pull --agent agt_0123456789
142
+ domino-agent pull governance-agent --agent governance-agent
143
+ ```
144
+
145
+ - The folder's default path is a new folder named after the agent's `name`. Give a path to write it in another place.
146
+ - The definition file has an ID line, `id: <the agent's ID>`. Nobody types it. After a commit, `domino-agent deploy` of the folder
147
+ connects it to the same agent, which keeps its ID, its tasks and its history.
148
+ - A wizard agent (one made in the agent service's UI or with its API) moves to git this way: `pull` it, commit the folder, then
149
+ `deploy` it.
150
+ - `pull` refuses to write into a folder that has files. `--force` writes into it: the agent's files replace them, and each known
151
+ file that the agent doesn't have (`instructions.md`, a skill's file, a subagent file) is removed, so that an old one doesn't
152
+ deploy. Other files, such as a README, stay.
153
+ - `pull` refuses a framework agent: an agent folder holds only harness agents for now.
154
+
155
+ ## Changes
156
+
157
+ - 0.1.0: the first release. `deploy` and `pull`; the definition file; own skills, store skills and custom subagents.
158
+
159
+ ## License
160
+
161
+ Apache-2.0. Copyright 2026 Domino Data Lab, Inc. The LICENSE and NOTICE files are in the package.
@@ -0,0 +1,4 @@
1
+ """domino-agent: the command for an agent folder in git. `domino-agent deploy` registers an agent folder in the agent service, and
2
+ `domino-agent pull` writes one from an agent that exists. The folder format is `domino_agent.folder_format`, which the agent service
3
+ imports too. Nothing here imports the agent service, so the package runs on a laptop or in a pipeline."""
4
+ __version__ = "0.1.0"
@@ -0,0 +1,6 @@
1
+ """`python -m domino_agent`: the same as the `domino-agent` command."""
2
+ import sys
3
+
4
+ from domino_agent.cli import main
5
+
6
+ sys.exit(main())
@@ -0,0 +1,27 @@
1
+ """The `domino-agent` command line. Each command is a module with `add(subparsers)` and `run(args, env) -> exit code`.
2
+ Exit codes: 0 done, 1 refused or failed (the output says why), 2 a wrong command line."""
3
+ import argparse
4
+ import os
5
+ import sys
6
+
7
+ from domino_agent import __version__, deploy, pull
8
+
9
+ COMMANDS = [deploy, pull] # a later command is a module of the same form, added here
10
+
11
+
12
+ def parser():
13
+ p = argparse.ArgumentParser(prog="domino-agent", description="Work with an agent folder in git and the Domino agent service.")
14
+ p.add_argument("--version", action="version", version=f"domino-agent {__version__}")
15
+ sub = p.add_subparsers(dest="command", metavar="<command>")
16
+ for c in COMMANDS:
17
+ c.add(sub)
18
+ return p
19
+
20
+
21
+ def main(argv=None, env=None):
22
+ p = parser()
23
+ args = p.parse_args(sys.argv[1:] if argv is None else argv)
24
+ if not args.command:
25
+ p.print_help()
26
+ return 2
27
+ return args.run(args, os.environ if env is None else env)