Skip to content

OMP target does not follow profile-scoped agent directory #259

Description

@thinhngotony

Summary

The omp target syncs agents to a fixed path, /Users/tony/.omp/agent/agents, but OMP can run with a profile-scoped agent directory such as /Users/tony/.omp/profiles/copilot/agent. In that layout, skillshare sync reports the agents as linked while the active OMP session cannot discover or spawn them.

Evidence

On OMP 17.2.7:

skillshare target list --json
{
  "name": "omp",
  "agentPath": "/Users/tony/.omp/agent/agents",
  "agentSync": "5/5 linked",
  "agentLinkedCount": 5
}

The active profile uses:

/Users/tony/.omp/profiles/copilot/agent

The profile has no agents/ directory, while the static target contains all five linked agent files. As a result, the OMP task tool exposes only bundled agents (scout, designer, reviewer, security-reviewer, librarian, task, sonic), not the synced custom agents (dev, manager, qa, etc.). The same mismatch applies to the other profiles (hyberorbit and omp-cisco).

Reproduction

  1. Configure custom agents in the Skillshare source.
  2. Configure the omp target with the current static agent path /Users/tony/.omp/agent/agents.
  3. Run OMP with a profile whose agent directory is /Users/tony/.omp/profiles/<profile>/agent.
  4. Run skillshare target list --json; it reports 5/5 linked.
  5. Start OMP and inspect /agents or invoke task with agent: "dev".
  6. The custom agent is absent because it is outside the active profile's discovery root.

Expected behavior

The OMP target should sync agents into the active profile's agent directory, or provide an explicit profile-aware target configuration. A single static target should not report success when it is disconnected from the active OMP profile.

Proposed solutions

  • Resolve the OMP agent path from the active profile, e.g. /Users/tony/.omp/profiles/<profile>/agent/agents; or
  • Support multiple OMP profile targets / a path template; or
  • Document and validate the required omp profile setup, failing or warning when the configured target is not the active OMP agent directory.

The fix should preserve existing non-profile OMP installations and avoid silently creating a second source of truth.

Environment

  • macOS arm64
  • skillshare target omp
  • OMP 17.2.7
  • Three OMP profiles: copilot, hyberorbit, omp-cisco

Related: #184 (Copilot CLI target missing agents path).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions