feat(packages): { packageDir } software refs read from agentos-package.json#1561
Merged
Conversation
4f724c4 to
7ccbac5
Compare
|
🚅 Deployed to the agentos-pr-1561 environment in agentos
🚅 Environment agentos-pr-1561 in rivet-frontend has no services deployed. |
7ccbac5 to
c5ad021
Compare
c5ad021 to
7f2a53f
Compare
7f2a53f to
f76b28a
Compare
f76b28a to
35de394
Compare
35de394 to
bdcafdd
Compare
bdcafdd to
1dd6baa
Compare
85d975a to
bcd5f3d
Compare
1dd6baa to
90fea52
Compare
…e.json
- software entries are { packageDir } objects (SoftwarePackageRef from @agentos-software/manifest); name/agent/provides move into the package's agentos-package.json, read by the sidecar
- client forwards only the package dir on the wire; agent configs derived from agentos-package.json
- registry packages, examples, and RivetKit actor updated to the { packageDir } shape
- docs updated to the { packageDir } + agentos-package.json model
90fea52 to
c324898
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ConfigureVm.packages+LinkPackage); the client is a thin forwarder with no client-side staging{name, dir}software model; remove legacy software types,SoftwareContext, and theagentos-package.jsonmanifest path@agentos-software/*to the new preview (both version tracks)posix,python); migrate docs to@rivet-dev/docs-theme+ new architecture pagespublish.yaml+darwin.Dockerfile: exclude@agentos/websitefrom the frozen installs (the docs-theme website vendor is materialized only inci.yml)pack-agents: resolve the toolchain from the sibling secure-exec checkout or the published@rivet-dev/agentos-toolchain, and skip with a warning if neither is present (built-in agents are optional shipped artifacts)ConfigureVmRequestfields (packages,packagesMountAt)Verified end-to-end against the published preview: a temp project
npm installs@rivet-dev/agentos-core, runs the quickstart (AgentOs.create+ file I/O, auto-projecting@agentos-software/common) and the custom-software flow (agentos-toolchain pack+defineSoftware+exec) — both pass.Known gaps (follow-up): the
@agentos-software/*command/agent packages and@rivet-dev/agentos-toolchainhave no CI publish path; for the preview validating this change they were published from a local machine, not CI. Wiring the toolchain into the Publish-npm job (so releases bundle the built-in agents) is a follow-up.Additional changes on this revision:
{name, dir}model (removetype/wasm-commands/commandDir/packageDir); reorder the Software Definition quickstart (WebAssembly before Node.js)