should register working_dir capability before initializing a session

[payneio]

I have a problem I can't solve in my bundle:

1 hooks-logging captures session.working_dir capability at mount time (during session.initialize())
2 The foreman registers this capability AFTER create_session() returns
3 So hooks-logging sees None and falls back to Path.cwd(), which is wrong for spawned workers

The Fix: Fix in amplifier-foundation

In amplifier_foundation/bundle.py, register the capability BEFORE initialize():

Around line 1033-1039, add this BEFORE initialize():

# Register working directory capability BEFORE initialize() so hooks can use it
# This ensures hooks-logging writes to the correct project directory for spawned sessions
effective_cwd = session_cwd or self.bundle.base_path or Path.cwd()
session.coordinator.register_capability(
    "session.working_dir", str(effective_cwd)
)

# Initialize the session (loads all modules)
await session.initialize()

[bkrabach]

Thanks for the detailed report @payneio!

I investigated this issue and found that the capability registration is already implemented correctly in the current codebase:

Current behavior (already correct):

• create_session() registers session.working_dir at bundle.py:1048-1050 before session.initialize() at line 1053
• spawn() registers session.working_dir at bundle.py:1252-1254 before child_session.initialize() at line 1256
• Child sessions inherit working_dir from their parent session (line 1246)

Verification:
I ran a smoke test that:

1. Created a session from /tmp/issue201-test
2. Spawned a child session via the task tool
3. Verified both parent AND child logs were written to ~/.amplifier/projects/-tmp-issue201-test/sessions/

The test passed - hooks-logging correctly receives the capability in spawned sessions.

---

Questions to help diagnose your issue:

1. What version of amplifier-foundation are you running? (The fix was added in commit eaf0997 on 2025-01-25)

2. You mention "the foreman" registers the capability - is this custom app-layer code? If you're creating AmplifierSession objects directly (bypassing PreparedBundle.create_session() / spawn()), you would need to register the capability yourself before calling session.initialize().

3. Could you share more details about your session creation flow? Are you using:

   • PreparedBundle.create_session() / spawn() (foundation)
   • Direct AmplifierSession instantiation (core)
   • Custom app-layer orchestration

Happy to help debug further once we understand your specific setup!

[bkrabach]

Follow-up: Based on additional context that you may be using a custom orchestrator ("the foreman"), I tested the manual registration approach and confirmed it works.

If your foreman creates AmplifierSession directly (bypassing PreparedBundle), you can register the capability yourself before calling initialize():

from amplifier_core import AmplifierSession
from pathlib import Path

# Your custom orchestrator creates the session
session = AmplifierSession(mount_plan)

# Register working_dir capability BEFORE initialize()
working_dir = Path("/path/to/your/project")
session.coordinator.register_capability(
    "session.working_dir", str(working_dir.resolve())
)

# Now initialize - hooks will see the capability
await session.initialize()

I verified this in a smoke test:

• Created AmplifierSession directly (no PreparedBundle)
• Registered capability manually before initialize()
• Confirmed hooks-logging wrote to the correct project directory (-tmp-custom-orchestrator-test/)
• Full event lifecycle captured correctly

This pattern matches what PreparedBundle.create_session() does internally at bundle.py:1048-1050.

Let me know if this solves your issue or if there's something else going on in your setup!