open-agent-relay 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,201 @@
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.
@@ -0,0 +1,314 @@
1
+ Metadata-Version: 2.4
2
+ Name: open-agent-relay
3
+ Version: 0.1.0
4
+ Summary: Let teammates call your local agent or automation directly over the LAN.
5
+ Author: ShakespeareLabs
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/ShakespeareLabs/open-agent-relay
8
+ Project-URL: Repository, https://github.com/ShakespeareLabs/open-agent-relay
9
+ Project-URL: Issues, https://github.com/ShakespeareLabs/open-agent-relay/issues
10
+ Project-URL: Documentation, https://github.com/ShakespeareLabs/open-agent-relay#readme
11
+ Keywords: agents,automation,lan,local-first,self-hosted
12
+ Classifier: Development Status :: 3 - Alpha
13
+ Classifier: Environment :: Console
14
+ Classifier: Intended Audience :: Developers
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Programming Language :: Python :: 3.11
17
+ Classifier: Programming Language :: Python :: 3.12
18
+ Classifier: Programming Language :: Python :: 3.13
19
+ Classifier: Programming Language :: Python :: 3.14
20
+ Classifier: Operating System :: OS Independent
21
+ Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
22
+ Classifier: Topic :: System :: Distributed Computing
23
+ Requires-Python: >=3.11
24
+ Description-Content-Type: text/markdown
25
+ License-File: LICENSE
26
+ Dynamic: license-file
27
+
28
+ # OpenAgentRelay
29
+
30
+ [English](README.md) | [简体中文](README.zh-CN.md)
31
+
32
+ > **Turn any local agent or automation into a team-callable capability.**
33
+
34
+ OpenAgentRelay lets a teammate or another Agent call something that already works on your computer. They install one small `relay` CLI; they do not need this repository, your Agent source code, its dependencies, prompts, or business credentials.
35
+
36
+ The `main` branch is an **Alpha for direct calls on a trusted LAN**. It uses plain HTTP and a shared key. Do not expose it to the public internet or connect it to production write operations.
37
+
38
+ ```text
39
+ Caller or caller Agent ── trusted LAN ──> Publisher's relay ──> Local Agent
40
+ ↑ |
41
+ └──────────────────────── result ─────────────────────────────┘
42
+ ```
43
+
44
+ ## Do not know how to use it? Send this link to your Agent
45
+
46
+ Send this project link directly to Codex, Claude Code, or another Agent that can read web pages:
47
+
48
+ ```text
49
+ https://github.com/ShakespeareLabs/open-agent-relay
50
+ ```
51
+
52
+ Then tell the Agent which role you need. It can read this README, install the `relay` CLI without cloning the repository, and guide or perform the setup.
53
+
54
+ For a publisher, copy this message:
55
+
56
+ ```text
57
+ Read https://github.com/ShakespeareLabs/open-agent-relay and help me publish
58
+ one existing local Agent as a trusted-LAN capability. Install only the relay CLI;
59
+ do not clone the repository. Start with the safe test, use a restricted workspace
60
+ and minimum credentials, then give me the Relay URL, Agent name, and the exact
61
+ connection block I should share. Stop and ask me before any security-sensitive choice.
62
+ ```
63
+
64
+ For a caller, send the connection details privately and copy this message:
65
+
66
+ ```text
67
+ Read https://github.com/ShakespeareLabs/open-agent-relay and help me call a shared
68
+ capability. Install only the relay CLI; do not clone the repository. Use --expect-agent
69
+ and --json, treat a nonzero exit code as failure, and never print the Access Key.
70
+
71
+ Relay URL: <URL from the publisher>
72
+ Agent name: <name from the publisher>
73
+ ```
74
+
75
+ Provide the Access Key through `RELAY_ACCESS_KEY`, not inside the message. The Agent needs this link plus the private connection details; it does not need OpenAgentRelay source code.
76
+
77
+ ## Install the CLI
78
+
79
+ Normal users do not need to clone the repository. Install the CLI with [`pipx`](https://pipx.pypa.io/):
80
+
81
+ ```bash
82
+ pipx install "git+https://github.com/ShakespeareLabs/open-agent-relay.git@main"
83
+ relay version
84
+ ```
85
+
86
+ If `pipx` is not installed, follow its one-time installation guide (`brew install pipx` on macOS is the common path).
87
+
88
+ If you are already inside a Python 3.11+ virtual environment, use:
89
+
90
+ ```bash
91
+ python -m pip install "git+https://github.com/ShakespeareLabs/open-agent-relay.git@main"
92
+ ```
93
+
94
+ Cloning the repository is only needed for development. After the first packaged release, the primary installation command will become `pipx install open-agent-relay`.
95
+
96
+ ## End-to-end examples
97
+
98
+ The [`examples/`](examples/) directory contains three reusable paths:
99
+
100
+ - a zero-dependency, read-only report over local CSV data;
101
+ - an ephemeral Codex review in a dedicated read-only workspace;
102
+ - a Claude Code review using non-interactive plan mode with write and web tools blocked.
103
+
104
+ Start with the local report to verify networking and authentication before connecting an Agent.
105
+
106
+ ## Publisher: share a capability
107
+
108
+ The publisher owns the working Agent or automation.
109
+
110
+ ### 1. Start with a safe test
111
+
112
+ Choose an Access Key of at least 16 characters without putting it in shell history:
113
+
114
+ ```bash
115
+ read -s RELAY_ACCESS_KEY
116
+ export RELAY_ACCESS_KEY
117
+ ```
118
+
119
+ Start a harmless test capability:
120
+
121
+ ```bash
122
+ relay serve \
123
+ --host 0.0.0.0 \
124
+ --port 8787 \
125
+ --name uppercase \
126
+ --description "Turn text into uppercase" \
127
+ -- python -c 'import sys; print(sys.stdin.read().upper())'
128
+ ```
129
+
130
+ Successful startup confirms that the configured key was loaded and prints `Serving uppercase on http://0.0.0.0:8787`. If no key was configured, Relay generates and prints a temporary one. Verify the service on the publisher's computer:
131
+
132
+ ```bash
133
+ curl http://127.0.0.1:8787/healthz
134
+ ```
135
+
136
+ The expected response is `{"status":"ok"}`.
137
+
138
+ ### 2. Share connection details
139
+
140
+ Find the publisher's LAN address. Common commands are `ipconfig getifaddr en0` on macOS or `hostname -I` on Linux. Send the caller exactly these values through a trusted channel:
141
+
142
+ ```text
143
+ Relay URL: http://192.168.1.42:8787
144
+ Agent name: uppercase
145
+ Access Key: <the RELAY_ACCESS_KEY value>
146
+ Purpose: Turn text into uppercase
147
+ Trust scope: Trusted LAN Alpha; no sensitive or production write requests
148
+ ```
149
+
150
+ `0.0.0.0` is a listen address, not the address callers should use. A firewall may also need to allow inbound TCP traffic on port 8787.
151
+
152
+ ### 3. Publish an existing command
153
+
154
+ Relay starts the command once for each request. The command must:
155
+
156
+ - read one request from standard input;
157
+ - write the final answer to standard output;
158
+ - write logs and diagnostics to standard error;
159
+ - exit when that request is finished.
160
+
161
+ ```bash
162
+ relay serve \
163
+ --host 0.0.0.0 \
164
+ --name ads-report \
165
+ --description "Read-only advertising report" \
166
+ -- python /path/to/ads_report.py
167
+ ```
168
+
169
+ ### 4. Publish a restricted Codex capability
170
+
171
+ Use a dedicated workspace and the minimum credentials needed for this one capability. Do not expose your everyday Codex environment with all personal files, MCP servers, Skills, and tokens.
172
+
173
+ ```bash
174
+ relay serve \
175
+ --host 0.0.0.0 \
176
+ --name code-reviewer \
177
+ --description "Read-only review of the dedicated workspace" \
178
+ -- codex exec \
179
+ --ephemeral \
180
+ --sandbox read-only \
181
+ --ignore-user-config \
182
+ --skip-git-repo-check \
183
+ -C /path/to/restricted-workspace \
184
+ -
185
+ ```
186
+
187
+ Each request normally starts a fresh `codex exec`. Codex can use what is available in that restricted workspace, but Relay does not automatically resume the publisher's historical Codex sessions.
188
+
189
+ ## Caller: call a capability
190
+
191
+ The caller only needs the `relay` CLI and the connection details. They do not need the publisher's repository or Agent implementation.
192
+
193
+ Load the shared key without placing it in command history:
194
+
195
+ ```bash
196
+ read -s RELAY_ACCESS_KEY
197
+ export RELAY_ACCESS_KEY
198
+ ```
199
+
200
+ ### Direct execution
201
+
202
+ For a person:
203
+
204
+ ```bash
205
+ relay ask \
206
+ --target http://192.168.1.42:8787 \
207
+ --expect-agent uppercase \
208
+ "hello team"
209
+ ```
210
+
211
+ For another Agent or automation, always request JSON:
212
+
213
+ ```bash
214
+ relay ask \
215
+ --target http://192.168.1.42:8787 \
216
+ --expect-agent uppercase \
217
+ --json \
218
+ "hello team"
219
+ ```
220
+
221
+ Successful JSON output:
222
+
223
+ ```json
224
+ {
225
+ "capability": "uppercase",
226
+ "result": "HELLO TEAM"
227
+ }
228
+ ```
229
+
230
+ ### Deep interaction
231
+
232
+ Direct calls are stateless by default. Start a Relay-managed conversation when follow-up questions need prior context:
233
+
234
+ ```bash
235
+ relay ask \
236
+ --target http://192.168.1.42:8787 \
237
+ --expect-agent ads-report \
238
+ --new-conversation \
239
+ --json \
240
+ "Analyze this account"
241
+ ```
242
+
243
+ Save the returned `conversation_id`, then continue:
244
+
245
+ ```bash
246
+ relay ask \
247
+ --target http://192.168.1.42:8787 \
248
+ --expect-agent ads-report \
249
+ --conversation conv_... \
250
+ --json \
251
+ "Which campaign is worst?"
252
+ ```
253
+
254
+ Relay stores a bounded text transcript in memory and injects it into a fresh Agent execution. Conversations expire after one hour by default and disappear when the server restarts. The local Caller ID prevents accidental cross-caller continuation; it is not authenticated personal identity.
255
+
256
+ ## Give this capability to another Agent
257
+
258
+ Configure `RELAY_ACCESS_KEY` in the caller Agent's environment, then give it this connection block:
259
+
260
+ ```text
261
+ You can call a remote capability with the relay CLI.
262
+
263
+ Target: http://192.168.1.42:8787
264
+ Expected Agent: ads-report
265
+
266
+ For a one-shot request, run:
267
+ relay ask --target http://192.168.1.42:8787 --expect-agent ads-report --json "<request>"
268
+
269
+ For follow-ups, start with --new-conversation, save conversation_id from the JSON,
270
+ then use --conversation <conversation_id>. Treat a nonzero exit code as failure.
271
+ Do not print or return RELAY_ACCESS_KEY.
272
+ ```
273
+
274
+ The Agent needs the CLI and connection block, not the OpenAgentRelay repository.
275
+
276
+ ## Errors and retry behavior
277
+
278
+ Operational CLI failures exit nonzero and write a JSON error to standard error:
279
+
280
+ ```json
281
+ {"error":{"status":401,"code":"UNAUTHORIZED","message":"a valid access key is required"}}
282
+ ```
283
+
284
+ Common codes:
285
+
286
+ | Code | Meaning | Caller action |
287
+ |---|---|---|
288
+ | `CONNECTION_ERROR` | Wrong address, server stopped, or firewall blocked | Check the URL, LAN, server, and port |
289
+ | `UNAUTHORIZED` | Missing or incorrect Access Key | Reload the shared key |
290
+ | `AGENT_MISMATCH` | The public Agent name differs | Stop and confirm the publisher |
291
+ | `BUSY` | Execution concurrency is full | Retry later with backoff |
292
+ | `EXECUTION_TIMEOUT` | The local Agent exceeded its time limit | Ask the publisher or simplify the request |
293
+ | `OUTPUT_TOO_LARGE` | The Agent exceeded its output limit | Ask for a smaller result |
294
+
295
+ The public Agent Card is available at `/.well-known/agent-card.json`. A browser user can also open the Relay URL and enter the Access Key.
296
+
297
+ ## Security boundary
298
+
299
+ - Bearer authentication uses one shared key; it does not identify individual teammates.
300
+ - Transport is plain HTTP. Anyone who can observe the LAN traffic may see the key, input, and output.
301
+ - `--expect-agent` prevents configuration mistakes; it does not cryptographically prove server identity.
302
+ - Caller input is untrusted. A capable Agent may read files, call tools, or disclose data that its process can access.
303
+ - Use a dedicated workspace, read-only tools, minimal credentials, and a narrowly described capability.
304
+ - Do not expose the port to the public internet or attach production write operations.
305
+
306
+ Read [SECURITY.md](SECURITY.md) before serving a real Agent.
307
+
308
+ ## Limits and current scope
309
+
310
+ `relay serve --help` exposes execution timeout, request size, output size, concurrency, and conversation expiry controls. Version 0.1 does not include TLS, per-user permissions, automatic discovery, file transfer, progress streaming, durable conversations, multiple Agents behind one address, or a sandbox supplied by Relay.
311
+
312
+ The asynchronous Hub + Runner experiment remains on the [`hub-mode` branch](https://github.com/ShakespeareLabs/open-agent-relay/tree/hub-mode). It is not part of this direct-mode Alpha path.
313
+
314
+ For source development, see [CONTRIBUTING.md](CONTRIBUTING.md). Licensed under Apache-2.0.