Prose Assistant Lab Environment Access

If the Prose Assistant work reaches the point where AG needs direct access to Debbie (Claude Code) on Lab PC 2, the preferred approach is to give him a separate development identity rather than access to Tony's existing Windows or Claude sessions.

1) Separate Windows account on Lab PC 2

AG should have his own Windows account on the Beelink PC. This account should be a standard user account, not an administrator account.

The Windows account becomes the primary security boundary. It determines which folders and system resources AG — and Claude Code acting on his behalf — can access.

The account can be given modify rights to the Prose Assistant development area while keeping system directories and unrelated AI Lab management files inaccessible.

2) Separate Claude account

AG should authenticate Claude Code using his own Anthropic/Claude account, rather than Tony's account.

This keeps AG's authentication, usage, limits, and Claude activity separate from Tony's and avoids sharing Tony's Claude credentials.

3) Intended access path

The target arrangement would be:

Tony's Windows account → Debbie / Claude Code → Tony's Claude account → full AI Lab access
AG's home computer → SSH → AG's Beelink Windows account → AG's Claude Code session → AG's Claude account → Prose Assistant development access

This lets both people use Claude Code on the same machine while keeping their identities and permissions separate.

4) Scope AG's access to Prose Assistant work

The goal is not to give AG general administrative access to Lab PC 2. His environment should be set up specifically for Prose Assistant development and experimentation.

Where practical, AG's account should have access to:

System-level changes and unrelated AI Lab areas should remain outside that scope unless explicitly approved.

5) Important Ollama limitation

A separate Windows account does not automatically isolate AG from Ollama.

Ollama is running locally on Lab PC 2 and its local API does not provide per-Windows-user authorization. A local shell session may therefore be able to interact with Ollama even when Windows file permissions are carefully restricted.

This is the most important technical issue to resolve before AG is given a Claude Code shell on the machine. Jason and Debbie should review how much Ollama access AG actually needs and what safeguards are practical.

6) Start with the least access required

The current Strawman Design calls for first determining how much of the Prose Assistant behavior can be implemented and tested directly in Open WebUI.

If AG can perform the necessary Step 4 experiments described in the Prose Assistant Strawman Design Approach there, he may not initially need Claude Code access at all.

If those experiments demonstrate that Open WebUI is not sufficient — for example, because application code is required for mode control, state management, context assembly, or other behavior — then the separate Windows account and separate Claude account provide the preferred path to giving AG direct access to Debbie.

Overall Access Principle

AG should have his own identity at both layers:

Windows account — controls what AG and Claude Code can do on Lab PC 2.

Claude account — controls AG's relationship with Anthropic and Claude Code.

AG should not be given Tony's Windows credentials or simply be placed into Tony's existing Debbie session. Doing so would remove most of the security and accountability benefits of creating a separate development environment.