Preserve the ~/projects workspace surface in standalone AOS #925

New issue

Closed

opened 2026-08-06 03:50:48 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-06 03:50:48 +00:00

Owner

Problem

Kai normally works from ~/projects. A native AOS or acompose launch preserves the fleet-shaped projects surface, while standalone aoscompose mounts only the current working directory as one workspace path.

Launching from the usual projects root should not discard the working topology Kai relies on for adjacent repositories, cross-repo context, and normal navigation.

Desired outcome

Make standalone AOS expose a safe, predictable ~/projects-equivalent workspace surface when the launch begins from the projects root, with the selected repository remaining the active working directory.

Acceptance signals

A launch from the projects root provides the expected owner/repository hierarchy inside the container.
A launch from a repository subdirectory selects its corresponding workspace while retaining the approved surrounding projects surface.
The behavior is documented alongside the existing CWD mount contract.
The implementation does not widen repository write access beyond the composed residency plan.

## Problem Kai normally works from `~/projects`. A native AOS or `acompose` launch preserves the fleet-shaped projects surface, while standalone `aoscompose` mounts only the current working directory as one workspace path. Launching from the usual projects root should not discard the working topology Kai relies on for adjacent repositories, cross-repo context, and normal navigation. ## Desired outcome Make standalone AOS expose a safe, predictable `~/projects`-equivalent workspace surface when the launch begins from the projects root, with the selected repository remaining the active working directory. ## Acceptance signals * A launch from the projects root provides the expected owner/repository hierarchy inside the container. * A launch from a repository subdirectory selects its corresponding workspace while retaining the approved surrounding projects surface. * The behavior is documented alongside the existing CWD mount contract. * The implementation does not widen repository write access beyond the composed residency plan.

~~coilyco-ops referenced this issue 2026-08-06 06:19:27 +00:00~~

Use native shadow workspaces for standalone AOS #942

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-06 06:24:27 +00:00

Use native shadow workspaces for standalone AOS #942

coilyco-ops commented

2026-08-06 06:55:34 +00:00

Author

Owner

Landed on main in coilyco-flight-deck/agentic-os@53b035bbb9.

Validation passed locally through ward exec aos-test, ward exec aos-build, ward exec aos-lint, ward exec test, ward exec pre-commit-all, and the AOS release build/package/check verbs. Pull request #942 was green before landing.

Landed on main in coilyco-flight-deck/agentic-os@53b035bbb969995bc2780e6971f2b95b30fe9bb2. Validation passed locally through ward exec aos-test, ward exec aos-build, ward exec aos-lint, ward exec test, ward exec pre-commit-all, and the AOS release build/package/check verbs. Pull request #942 was green before landing.

coilyco-ops closed this issue

2026-08-06 06:55:35 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#925

No description provided.

Rows
Columns