Skip to content

Agent home repos should expose agent:list so shimmer as works from home dirs #758

Description

@brownie-ricon

Summary

While testing local agent fanout, shimmer as junior failed when invoked from ~/agents/junior/home because that home repo does not provide an agent:list task:

Error: could not list agents.
Does /Users/rikonor/agents/junior/home provide an 'agent:list' task?
agent:list stderr:
  mise ERROR no task agent:list found

Running the same command from a fold clone succeeds.

Why this matters

Local async wakes need to set the target agent identity before starting shimmer agent --headless in that agent's home repo. If shimmer as <agent> depends on the current repo having agent:list, the obvious invocation shape fails from the target home. If callers ignore the failure, they can start a headless session in another agent's workspace under the wrong identity.

Expected

One of:

  • shimmer as <agent> should resolve agents independently of caller cwd; or
  • shimmer as <agent> should provide a clear --repo / --agent-list-repo option; or
  • docs/help should explicitly say to run it from fold/den and automation should fail closed if identity setup fails.

Related pattern note

Captured the local workflow guardrail in fold local-async-agent-wake: evaluate shimmer as from a fold clone, never print its secret-bearing output, and run the headless wake in a background process with a completion signal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions