You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ed4d026
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ User mental model:
38
38
* A worker is a remote runtime destination.
39
39
* Connecting to a worker happens through `Add worker` -> `Connect remote` using URL + token (or deep link).
40
40
41
-
Read INFRASTRUCTURE.md
41
+
Read `ARCHITECTURE.md` for runtime flow, server-vs-shell ownership, and architecture behavior. Read `INFRASTRUCTURE.md` for deployment and control-plane details.
42
42
43
43
## Why OpenWork Exists
44
44
@@ -126,12 +126,13 @@ Design principles for hot reload:
126
126
## Repository Guidance
127
127
128
128
* Use `VISION.md`, `PRINCIPLES.md`, `PRODUCT.md`, `ARCHITECTURE.md`, and `INFRASTRUCTURE.md` to understand the "why" and requirements so you can guide your decisions.
129
+
* Treat `ARCHITECTURE.md` as the authoritative system design source for runtime flow, server ownership, filesystem mutation policy, and agent/runtime boundaries. If those behaviors change, update `ARCHITECTURE.md` in the same task.
129
130
* Use `DESIGN-LANGUAGE.md` as the default visual reference for OpenWork app and landing work.
130
131
* For OpenWork session-surface details, also reference `packages/docs/orbita-layout-style.mdx`.
131
132
132
133
## Dev Debugging
133
134
134
-
* If you change `packages/server/src`, rebuild the OpenWork server binary (`pnpm --filter openwork-server build:bin`) because `openwork` (openwork-orchestrator) runs the compiled server, not the TS sources.
135
+
* If you change `apps/server/src`, rebuild the OpenWork server binary (`pnpm --filter openwork-server build:bin`) because `openwork` (openwork-orchestrator) runs the compiled server, not the TS sources.
135
136
136
137
## Local Structure
137
138
@@ -144,7 +145,7 @@ openwork/
144
145
ARCHITECTURE.md # Runtime modes and OpenCode integration
145
146
.gitignore # Ignores vendor/opencode, node_modules, etc.
146
147
.opencode/
147
-
packages/
148
+
apps/
148
149
app/
149
150
src/
150
151
public/
@@ -154,6 +155,9 @@ openwork/
154
155
desktop/
155
156
src-tauri/
156
157
package.json
158
+
server/
159
+
src/
160
+
package.json
157
161
```
158
162
159
163
## OpenCode SDK Usage
@@ -190,7 +194,7 @@ Key primitives to expose:
190
194
191
195
## Skill: SolidJS Patterns
192
196
193
-
When editing SolidJS UI (`packages/app/src/**/*.tsx`), consult:
197
+
When editing SolidJS UI (`apps/app/src/**/*.tsx`), consult:
194
198
195
199
*`.opencode/skills/solidjs-patterns/SKILL.md`
196
200
@@ -206,11 +210,11 @@ OpenWork releases are built by GitHub Actions (`Release App`). A release is trig
206
210
1. Ensure `main` is green and up to date.
207
211
2. Bump versions (keep these in sync):
208
212
209
-
*`packages/app/package.json` (`version`)
210
-
*`packages/desktop/package.json` (`version`)
211
-
*`packages/orchestrator/package.json` (`version`, publishes as `openwork-orchestrator`)
@@ -244,11 +248,11 @@ Confirm the DMG assets are attached and versioned correctly.
244
248
This is usually covered by `Release App` when `publish_sidecars` + `publish_npm` are enabled. Use `.opencode/skills/openwork-orchestrator-npm-publish/SKILL.md` for manual recovery or one-off publishing.
245
249
246
250
1. Ensure the default branch is up to date and clean.
Copy file name to clipboardExpand all lines: ARCHITECTURE.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,11 @@ Auto-detection can exist as a convenience, but should be tiered and explainable:
30
30
31
31
The readiness check should be a clear, single command (e.g. `docker info`) and the UI should show the exact error output when it fails.
32
32
33
+
## Minimal use of Tauri
34
+
We move most of the functionality to the openwork server which interfaces mostly with FS and proxies to opencode.
35
+
36
+
37
+
33
38
## Filesystem mutation policy
34
39
35
40
OpenWork should route filesystem mutations through the OpenWork server whenever possible.
@@ -47,6 +52,36 @@ Guidelines:
47
52
- If a feature cannot yet write through the OpenWork server, treat that as an architecture gap and close it before depending on direct local writes.
48
53
- Reads can fall back locally when necessary, but writes should be designed around the OpenWork server path.
49
54
55
+
## Agent authority map
56
+
57
+
When OpenWork is edited from `openwork-enterprise`, architecture and runtime behavior should be sourced from this document.
58
+
59
+
| Entry point | Role | Architecture authority |
60
+
| --- | --- | --- |
61
+
|`openwork-enterprise/AGENTS.md`| OpenWork Factory multi-repo orchestration | Defers OpenWork runtime flow, server-vs-shell ownership, and filesystem mutation behavior to `_repos/openwork/ARCHITECTURE.md`. |
62
+
|`openwork-enterprise/.opencode/agents/openwork-surgeon.md`| Surgical fix agent for `_repos/openwork`| Uses `_repos/openwork/ARCHITECTURE.md` as the runtime and architecture source of truth before changing product behavior. |
63
+
|`_repos/openwork/AGENTS.md`| Product vocabulary, audience, and repo-local development guidance | Refers to `ARCHITECTURE.md` for runtime flow, server ownership, and architectural boundaries. |
64
+
| Skills / commands / agents that mutate workspace state | Capability layer on top of the product runtime | Should assume the OpenWork server path is canonical for workspace creation, config writes, `.opencode/` mutation, and reload signaling. |
65
+
66
+
### Agent access to server-owned behavior
67
+
68
+
Agents, skills, and commands should model the following as OpenWork server behavior first:
69
+
70
+
- workspace creation and initialization
71
+
- writes to `.opencode/`, `opencode.json`, and `opencode.jsonc`
- reload event generation after config or capability changes
74
+
- other filesystem-backed capability changes that must work across desktop host mode and remote clients
75
+
76
+
Tauri or other native shell behavior remains the fallback or shell boundary for:
77
+
78
+
- file and folder picking
79
+
- reveal/open-in-OS affordances
80
+
- updater and window management
81
+
- host-side process supervision and native runtime bootstrapping
82
+
83
+
If an agent needs one of the server-owned behaviors above and only a Tauri path exists, treat that as an architecture gap to close rather than a parallel capability surface to preserve.
0 commit comments