Skip to content

plan(project-server): Phase 0 spike results and the design change they force - #106

Merged
androidand merged 2 commits into
devfrom
spike/project-server
Oct 2, 2026
Merged

androidand merged 2 commits into
devfrom
spike/project-server

Conversation

@androidand

Copy link
Copy Markdown
Owner

Docs only: openspec/changes/project-server/findings.md and ticked tasks.

Measured on a throwaway isolated server (no provider configured; single runs): one server hosts two worktrees under a shared projectID; sessions survive a hard kill but loops do not; only per-directory state needs a roster; an idle headless server is ~0.5% CPU and 318 MB; but each registered session spawns its own ~204 MB sidecar process, so in-server delivery alone would not deliver the memory argument. The plan gains a task to host the sockets inside the server.

Not tested: opencode attach (needs a terminal) and the 4-hour memory run.

🤖 Generated with Claude Code

…forced

One server hosts both worktrees under a shared projectID; sessions survive a
hard kill but loops do not; only per-directory state needs a roster; headless
sessions register as peers only after their first status, and each costs a
204 MB sidecar process, so in-server delivery alone does not deliver the
memory argument and the sockets must be hosted in the server.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

Hey! Your PR title plan(project-server): Phase 0 spike results and the design change they force doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

…t caveat up front

Review found the claim that sessions register only after their first status
contradicted the lifecycle code. Re-tested: a session created in a running
server registers within ~4s; the earlier observation was the resume-from-
history recovery path. Sidecar cost remeasured with three fresh sessions
(~172 MB each). The no-provider caveat moves to the top.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@androidand
androidand merged commit 09fa290 into dev Oct 2, 2026
2 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant