agent-status 0.1.4__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.
- agent_status-0.1.4/LICENSE +190 -0
- agent_status-0.1.4/PKG-INFO +297 -0
- agent_status-0.1.4/README.md +273 -0
- agent_status-0.1.4/agent_status.egg-info/PKG-INFO +297 -0
- agent_status-0.1.4/agent_status.egg-info/SOURCES.txt +11 -0
- agent_status-0.1.4/agent_status.egg-info/dependency_links.txt +1 -0
- agent_status-0.1.4/agent_status.egg-info/entry_points.txt +2 -0
- agent_status-0.1.4/agent_status.egg-info/requires.txt +1 -0
- agent_status-0.1.4/agent_status.egg-info/top_level.txt +1 -0
- agent_status-0.1.4/agent_status.py +629 -0
- agent_status-0.1.4/pyproject.toml +35 -0
- agent_status-0.1.4/setup.cfg +4 -0
- agent_status-0.1.4/tests/test_agent_status.py +520 -0
|
@@ -0,0 +1,190 @@
|
|
|
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 the 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 the 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 any 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
|
+
Copyright 2026 astatus contributors
|
|
179
|
+
|
|
180
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
181
|
+
you may not use this file except in compliance with the License.
|
|
182
|
+
You may obtain a copy of the License at
|
|
183
|
+
|
|
184
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
185
|
+
|
|
186
|
+
Unless required by applicable law or agreed to in writing, software
|
|
187
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
188
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
189
|
+
See the License for the specific language governing permissions and
|
|
190
|
+
limitations under the License.
|
|
@@ -0,0 +1,297 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: agent-status
|
|
3
|
+
Version: 0.1.4
|
|
4
|
+
Summary: Local agent status reference implementation
|
|
5
|
+
Author: astatus contributors
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/julsemaan/astatus
|
|
8
|
+
Project-URL: Repository, https://github.com/julsemaan/astatus
|
|
9
|
+
Project-URL: Issues, https://github.com/julsemaan/astatus/issues
|
|
10
|
+
Keywords: agent,status,local,a2a,cli
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: Programming Language :: Python :: 3
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
18
|
+
Classifier: Topic :: Software Development :: Libraries
|
|
19
|
+
Requires-Python: >=3.10
|
|
20
|
+
Description-Content-Type: text/markdown
|
|
21
|
+
License-File: LICENSE
|
|
22
|
+
Requires-Dist: rich>=13
|
|
23
|
+
Dynamic: license-file
|
|
24
|
+
|
|
25
|
+
# agent-status
|
|
26
|
+
|
|
27
|
+
`agent-status` is a generic local agent status standard with a small reference CLI. Core file format and validation logic stay lean. Display commands `list` and `watch` require `rich`; non-display commands like `emit`, `get`, `validate`, and `prune` work without it.
|
|
28
|
+
|
|
29
|
+
## Why a local status layer exists
|
|
30
|
+
|
|
31
|
+
Remote protocols answer remote questions. Local operators still need fast answers to a different set of questions: which agents are running here, what are they doing, and is the latest snapshot stale?
|
|
32
|
+
|
|
33
|
+
Why this needs its own standard:
|
|
34
|
+
- A2A is designed for remote discovery and task interaction, not workstation-local runtime visibility.
|
|
35
|
+
- Local operators need data that A2A does not model directly, such as process lifecycle, PID, workspace, and heartbeat freshness.
|
|
36
|
+
- One file per agent instance enables simple tooling: shell scripts, CLIs, watchers, and validators can all read the same shape.
|
|
37
|
+
- Shared writer and reader rules prevent ad hoc status files from drifting on filenames, fields, stale semantics, and shutdown behavior.
|
|
38
|
+
- `${XDG_STATE_HOME:-~/.local/state}` is a good fit for persistent user state that is local to a machine.
|
|
39
|
+
|
|
40
|
+
## Relation to A2A
|
|
41
|
+
|
|
42
|
+
This project is an A2A-compatible local status layer. It complements A2A rather than replacing it. It does not replace Agent Card discovery, Task APIs, or full A2A service behavior.
|
|
43
|
+
|
|
44
|
+
A2A answers, "How do agents talk to each other?" This repository answers, "What is running on this machine right now?"
|
|
45
|
+
|
|
46
|
+
See:
|
|
47
|
+
- `docs/agent-status-v1alpha1.md`
|
|
48
|
+
- `docs/a2a-compat.md`
|
|
49
|
+
|
|
50
|
+
## Install
|
|
51
|
+
|
|
52
|
+
Python 3.10+.
|
|
53
|
+
|
|
54
|
+
From PyPI:
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
pip install agent-status
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Manual setup:
|
|
61
|
+
|
|
62
|
+
```bash
|
|
63
|
+
python3 -m venv .venv
|
|
64
|
+
. .venv/bin/activate
|
|
65
|
+
pip install -e .
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Devbox alternative:
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
devbox shell
|
|
72
|
+
python -m pip install -e .
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Devbox uses same `.venv` path via `VENV_DIR=.venv`.
|
|
76
|
+
|
|
77
|
+
### Pi extension install
|
|
78
|
+
|
|
79
|
+
Pi package lives in `pi-extension/`, exported from repo root `package.json` like `ponytail`.
|
|
80
|
+
|
|
81
|
+
Install from local checkout:
|
|
82
|
+
|
|
83
|
+
```bash
|
|
84
|
+
pi install /path/to/astatus
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Do not install `./pi-extension` directly. Repo root `package.json` exports extension.
|
|
88
|
+
After install in running pi session, run `/reload` or restart pi so `session_start` fires for new extension.
|
|
89
|
+
|
|
90
|
+
Install from git:
|
|
91
|
+
|
|
92
|
+
```bash
|
|
93
|
+
pi install git:github.com/you/astatus
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
One-shot test without install:
|
|
97
|
+
|
|
98
|
+
```bash
|
|
99
|
+
pi -e ./pi-extension/index.js
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
## Build
|
|
103
|
+
|
|
104
|
+
Build a wheel and source distribution:
|
|
105
|
+
|
|
106
|
+
```bash
|
|
107
|
+
python -m pip install build
|
|
108
|
+
python -m build
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
Install from built wheel in a fresh environment:
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
python -m venv /tmp/astatus-smoke
|
|
115
|
+
. /tmp/astatus-smoke/bin/activate
|
|
116
|
+
pip install dist/*.whl
|
|
117
|
+
agent-status --help
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
## Quick start
|
|
121
|
+
|
|
122
|
+
Emit one snapshot:
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
RUN_ID="pi-$(python3 - <<'PY'
|
|
126
|
+
import uuid
|
|
127
|
+
print(uuid.uuid4().hex)
|
|
128
|
+
PY
|
|
129
|
+
)"
|
|
130
|
+
|
|
131
|
+
python3 -m agent_status emit \
|
|
132
|
+
--agent-id "$RUN_ID" \
|
|
133
|
+
--agent-name pi \
|
|
134
|
+
--lifecycle running \
|
|
135
|
+
--workspace "$PWD" \
|
|
136
|
+
--pid $$ \
|
|
137
|
+
--task-id task-123 \
|
|
138
|
+
--task-state working \
|
|
139
|
+
--task-summary "refactor scheduler tests" \
|
|
140
|
+
--task-status-timestamp 2026-06-20T16:44:55Z
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
`agent_id` must be unique per running agent instance. Do not derive it from PID alone: sandboxed sessions can share same PID and collide. `runtime.pid` is descriptive metadata only.
|
|
144
|
+
|
|
145
|
+
List snapshots:
|
|
146
|
+
|
|
147
|
+
```bash
|
|
148
|
+
python3 -m agent_status list
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
Get one snapshot:
|
|
152
|
+
|
|
153
|
+
```bash
|
|
154
|
+
python3 -m agent_status get "$RUN_ID"
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
Watch snapshots:
|
|
158
|
+
|
|
159
|
+
```bash
|
|
160
|
+
python3 -m agent_status watch --interval 2
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
Prune old stale or stopped snapshots:
|
|
164
|
+
|
|
165
|
+
```bash
|
|
166
|
+
python3 -m agent_status prune --prune-after 86400
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
Validate a file:
|
|
170
|
+
|
|
171
|
+
```bash
|
|
172
|
+
python3 -m agent_status validate examples/sample-status.json
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
## Protocol summary
|
|
176
|
+
|
|
177
|
+
Default status directory:
|
|
178
|
+
|
|
179
|
+
```text
|
|
180
|
+
${AGENT_STATUS_DIR:-${XDG_STATE_HOME:-~/.local/state}/agent-status}
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
One running agent instance maps to one file:
|
|
184
|
+
|
|
185
|
+
```text
|
|
186
|
+
<agent_id>.json
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
Core required fields:
|
|
190
|
+
- `schema_version`
|
|
191
|
+
- `agent_id`
|
|
192
|
+
- `agent_name`
|
|
193
|
+
- `runtime.lifecycle`
|
|
194
|
+
- `runtime.updated_at`
|
|
195
|
+
|
|
196
|
+
Task state uses A2A-style values. `idle`, `stale`, and `missing` are derived by readers and are never written directly.
|
|
197
|
+
|
|
198
|
+
## JSON example
|
|
199
|
+
|
|
200
|
+
```json
|
|
201
|
+
{
|
|
202
|
+
"schema_version": "agent-status/v1alpha1",
|
|
203
|
+
"agent_id": "pi-7d5d6ca5e54c44cfb9e8d5acfd3c71a1",
|
|
204
|
+
"agent_name": "pi",
|
|
205
|
+
"runtime": {
|
|
206
|
+
"lifecycle": "running",
|
|
207
|
+
"updated_at": "2026-06-20T16:45:00Z",
|
|
208
|
+
"last_activity_at": "2026-06-20T16:44:52Z",
|
|
209
|
+
"pid": 12345,
|
|
210
|
+
"workspace": "/home/julien/src/project"
|
|
211
|
+
},
|
|
212
|
+
"task": {
|
|
213
|
+
"id": "task-123",
|
|
214
|
+
"context_id": "ctx-456",
|
|
215
|
+
"state": "working",
|
|
216
|
+
"summary": "refactor scheduler tests",
|
|
217
|
+
"status_timestamp": "2026-06-20T16:44:55Z"
|
|
218
|
+
}
|
|
219
|
+
}
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
## CLI examples
|
|
223
|
+
|
|
224
|
+
After installation, you can also use the entry point directly:
|
|
225
|
+
|
|
226
|
+
```bash
|
|
227
|
+
agent-status emit --agent-id "pi-$(python3 - <<'PY'
|
|
228
|
+
import uuid
|
|
229
|
+
print(uuid.uuid4().hex)
|
|
230
|
+
PY
|
|
231
|
+
)" --agent-name pi --lifecycle running
|
|
232
|
+
agent-status list
|
|
233
|
+
agent-status get <agent-id>
|
|
234
|
+
agent-status watch
|
|
235
|
+
agent-status prune --prune-after 86400
|
|
236
|
+
agent-status validate examples/sample-status.json
|
|
237
|
+
```
|
|
238
|
+
|
|
239
|
+
## Writer rules
|
|
240
|
+
|
|
241
|
+
- Write the whole file atomically.
|
|
242
|
+
- `agent_id` must be unique per running instance. PID-only IDs like `pi-12345` are unsafe under PID namespaces or sandboxes.
|
|
243
|
+
- Use an absolute workspace path when it is known.
|
|
244
|
+
- Update on lifecycle changes, task changes, summary changes, and heartbeats.
|
|
245
|
+
- Send a heartbeat every 15 to 30 seconds.
|
|
246
|
+
- On clean exit, either remove the file or persist `runtime.lifecycle=stopped`.
|
|
247
|
+
- If you use temp files for atomic writes, temp names need random or OS-guaranteed uniqueness. Do not rely on PID suffixes.
|
|
248
|
+
|
|
249
|
+
## Stale semantics
|
|
250
|
+
|
|
251
|
+
The default `stale_after` value is 60 seconds.
|
|
252
|
+
|
|
253
|
+
A reader marks a record as stale when:
|
|
254
|
+
|
|
255
|
+
```text
|
|
256
|
+
now - runtime.updated_at > stale_after
|
|
257
|
+
```
|
|
258
|
+
|
|
259
|
+
If `runtime.lifecycle=running` and there is no `task`, a reader may render the agent as `idle`.
|
|
260
|
+
|
|
261
|
+
A stale file is not definitive proof that the writer is gone permanently. The agent may be crashed, suspended, disconnected, or simply slow. Readers should mark records as stale rather than deleting them silently. Cleanup is a separate operator policy.
|
|
262
|
+
|
|
263
|
+
The reference CLI provides explicit cleanup:
|
|
264
|
+
|
|
265
|
+
```bash
|
|
266
|
+
agent-status prune --prune-after 86400
|
|
267
|
+
```
|
|
268
|
+
|
|
269
|
+
The default prune policy removes snapshots older than 24 hours if they are already stale, along with older snapshots whose `runtime.lifecycle` is `stopped`.
|
|
270
|
+
|
|
271
|
+
## Validation
|
|
272
|
+
|
|
273
|
+
Run tests:
|
|
274
|
+
|
|
275
|
+
```bash
|
|
276
|
+
python3 -m unittest
|
|
277
|
+
```
|
|
278
|
+
|
|
279
|
+
Validate examples:
|
|
280
|
+
|
|
281
|
+
```bash
|
|
282
|
+
python3 -m agent_status validate examples/sample-status.json
|
|
283
|
+
python3 -m agent_status validate examples/a2a-linked-status.json
|
|
284
|
+
```
|
|
285
|
+
|
|
286
|
+
## Roadmap
|
|
287
|
+
|
|
288
|
+
Possible future additions:
|
|
289
|
+
- HTTP exporter
|
|
290
|
+
- registry bridge
|
|
291
|
+
- richer TUI or shell integrations
|
|
292
|
+
|
|
293
|
+
Out of scope for now:
|
|
294
|
+
- registry server
|
|
295
|
+
- full A2A server
|
|
296
|
+
- orchestration layer
|
|
297
|
+
- history store
|