Repository navigation
Home
Ubuntu edited this page Sep 25, 2026
·
3 revisions
Harness Nexus is a unified management platform for Agent-tool assets (Claude Code, Codex, DeepSeek, OpenCode, pi, Hermes …) across machines: consume upstream MCP servers once and re-expose one aggregated server to every tool, version skills/hooks/sub-agents/rules/MCP definitions into installable profiles, manage remote machines through a daemon, and chat with every agent from one portal.
This wiki holds the feature guides (what the product does — user-facing) and the development process docs (PRDs, technical designs, research notes, the historical roadmap).
- Source & README: sinrimin/harness-nexus
- How to contribute: CONTRIBUTING.md
- Code-coupled contract docs stay in the repo: docs/architecture.md and docs/adr/
| Guide | Covers |
|---|---|
| Authentication | users, roles, JWT sessions, personal access tokens |
| Credentials | named secrets, ${cred:…} injection, encryption at rest |
| MCP management | upstream servers, aggregated /mcp outlet, tool inspection |
| Profiles & installation | profile bundles, hnx install, the Claude Code marketplace emitter |
| Resources | skills, hooks, sub-agents, rules, commands |
| Skill hub | marketplace browse + multi-source skill search |
| LLM providers | provider routes, model discovery, multi-model |
| Machines & daemon | enrollment, the hnx daemon, inventory reports |
| Remote deploy & import | deploy jobs, inventory scan/diff/import |
| Portal chat | chatting with agents, sessions, the composer, permissions |
| Harness runtime management | installing/upgrading the agent CLIs, provider config push |
| Supported agents | the per-agent capability matrix |
- Documentation map — what PRD / design / research docs are, indexed by phase
- Web console design system — skeleton, content language and interaction rules of the console (issue #23)
- Skin system — the skin axis: tokens, hooks, the status device, the snapshot rig (issue #23)
- Historical roadmap — phase status through Phase 9 W16 (2026-09); forward planning now lives in issues + milestones
- Development workflow (issues, branches, verification, releases): CONTRIBUTING.md
The maintainer's local verification-rig notes (
test-rig.md) are machine-specific and deliberately unpublished.