tag-agent 0.1.0__tar.gz

tag_agent-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 TAG
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

tag_agent-0.1.0/MANIFEST.in

@@ -0,0 +1,9 @@
+include README.md
+include LICENSE
+include TODO.md
+include pyproject.toml
+recursive-include src/tag/assets *.yaml
+recursive-include src/tag/config *.yaml
+recursive-include src/tag/docs *.md
+recursive-include src/tag/patches *.patch
+recursive-include src/tag/vendor *.tar.gz

tag_agent-0.1.0/PKG-INFO

@@ -0,0 +1,229 @@
+Metadata-Version: 2.4
+Name: tag-agent
+Version: 0.1.0
+Summary: TAG: a Hermes-based orchestration layer with patched TUI, profile routing, and OpenRouter/Codex workflows.
+Author: TAG
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/sanskarpan/tag-agent
+Project-URL: Repository, https://github.com/sanskarpan/tag-agent.git
+Project-URL: Issues, https://github.com/sanskarpan/tag-agent/issues
+Keywords: agents,cli,codex,hermes,openrouter,orchestration,tui
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Classifier: Topic :: Terminals
+Requires-Python: <3.14,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Provides-Extra: dev
+Requires-Dist: build>=1.2.2; extra == "dev"
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: twine>=6.1.0; extra == "dev"
+Dynamic: license-file
+
+# TAG
+
+TAG is a standalone orchestration layer on top of Hermes. It packages the work
+done in this workspace into one installable CLI with:
+
+- a bundled Hermes source snapshot for first-run provisioning
+- managed Hermes bootstrap
+- shipped Hermes TUI patching
+- a custom `tag-control` skin
+- profile-based master/worker orchestration
+- OpenRouter worker routing
+- Codex import and runtime support
+- direct execution, Kanban execution, and benchmark history
+
+## Install
+
+```bash
+pip install tag-agent
+```
+
+This installs the `tag` command.
+
+For npm:
+
+```bash
+npm install -g tag-agent
+```
+
+For pnpm:
+
+```bash
+pnpm add -g tag-agent
+```
+
+The npm package installs a thin Node launcher for `tag`. On first run it
+creates an isolated Python runtime under `~/.tag/npm-runtime/<version>`,
+installs the bundled TAG Python package there, and then executes the same TAG
+CLI. That means the npm path still requires Python `>=3.11` and `<3.14` on
+`PATH`. The launcher will probe `python3.13`, `python3.12`, `python3.11`,
+`python3`, and `python` in that order on Unix-like systems.
+
+For a build artifact install:
+
+```bash
+python -m build
+pip install dist/tag_agent-0.1.0-py3-none-any.whl
+```
+
+For an npm artifact check:
+
+```bash
+npm pack
+```
+
+## First run
+
+```bash
+tag
+```
+
+Default behavior:
+
+1. create `~/.tag/config/tag.yaml` and the benchmark suite if missing
+2. extract the bundled Hermes snapshot into `~/.tag/managed/hermes-agent-upstream` if needed
+3. create a virtualenv for Hermes
+4. install Hermes with the required extras
+5. apply the TAG TUI patch
+6. install/build the Hermes TUI workspace
+7. bootstrap the default TAG profiles
+8. launch the orchestrator TUI
+
+The same managed bootstrap now happens automatically for non-TUI commands that
+need Hermes, for example:
+
+```bash
+tag submit --task-type mixed --execution direct --prompt "Reply with exactly: smoke-ok"
+tag benchmark --profile researcher --model-ref openrouter/deepseek/deepseek-v4-flash
+tag model --profile orchestrator -- list
+```
+
+For those commands, TAG provisions Hermes on demand and skips the TUI build if
+it is not needed, so `npm` is not required just to use submit/benchmark/model
+flows.
+
+If `tag` is started from a non-interactive context, it does not try to open the
+TUI blindly. It exits with a clear message and tells you to use `tag doctor`,
+`tag setup`, or `tag tui` from a real terminal.
+
+If you want the setup step explicitly:
+
+```bash
+tag setup
+tag tui
+```
+
+## Main commands
+
+```bash
+tag
+tag setup
+tag doctor
+tag bootstrap
+tag status
+tag assignments
+tag models --profile researcher
+tag openrouter-models --profile researcher --search gemini
+tag set-model --profile reviewer --ref openrouter/deepseek/deepseek-v4-pro
+tag submit --task-type mixed --execution direct --prompt "Reply with exactly: smoke-ok"
+tag benchmark --profile researcher --model-ref openrouter/deepseek/deepseek-v4-flash
+tag runs
+tag import-codex --profile orchestrator --codex-home ~/.codex
+tag chat --profile orchestrator -- --help
+tag config --profile orchestrator -- edit
+tag gateway --profile orchestrator -- start
+tag kanban --profile orchestrator -- list
+tag sessions --profile orchestrator -- list
+tag skills --profile orchestrator -- list
+tag plugins --profile orchestrator -- list
+tag tools --profile orchestrator -- list
+tag mcp --profile orchestrator -- list
+tag logs --profile orchestrator -- --since 1h
+tag dashboard --profile orchestrator -- --status
+tag memory --profile orchestrator -- status
+tag model --profile orchestrator -- list
+tag profile -- list
+tag completion --profile orchestrator -- zsh
+tag prompt-size --profile orchestrator
+tag update
+tag hermes --profile orchestrator -- gateway start
+tag tui --profile orchestrator
+```
+
+## Persistence
+
+TAG stores its managed state under `~/.tag` by default:
+
+- `config/tag.yaml`
+- `config/benchmark-suite.yaml`
+- `managed/hermes-agent-upstream`
+- `runtime/home`
+- `runtime/tag.sqlite3`
+
+Override the root with:
+
+```bash
+export TAG_HOME=/some/other/location
+```
+
+## Notes
+
+- The managed Hermes checkout remains Hermes internally; TAG is the packaged
+  experience and command surface around it.
+- TAG does not require a preinstalled Hermes checkout. By default it provisions
+  Hermes from a bundled source snapshot and only falls back to `git clone` if
+  that snapshot is unavailable.
+- If TAG can already discover a valid local Hermes source checkout, it will
+  reuse it automatically instead of forcing a second separate install.
+- If a real Codex CLI home already exists with `auth.json`, TAG imports that
+  into the managed orchestrator profiles automatically during setup.
+- The shipped patch only touches Hermes TUI skin handling and profile-aware
+  chrome.
+- OpenRouter keys and Codex auth remain per-profile concerns.
+- TAG currently targets Python `>=3.11` and `<3.14` and expects `npm` for full first-run
+  bootstrap because Hermes' TUI workspace is built locally. `git` is still
+  recommended for Hermes features like worktrees and for refresh/update flows,
+  but it is no longer required for the default bundled install path.
+- `tag update` is lifecycle-aware:
+  - on a bundled Hermes checkout, it refreshes the managed runtime from the
+    packaged snapshot and rebuilds it
+  - on a git-backed checkout, it delegates to Hermes' own update flow
+- The npm distribution is a launcher wrapper around the Python package, not a
+  separate Node reimplementation.
+
+## Command strategy
+
+TAG currently has three layers of command surface:
+
+1. Native TAG orchestration commands
+   - `setup`, `doctor`, `bootstrap`, `route`, `submit`, `benchmark`, `runs`
+2. High-value managed Hermes wrappers
+   - `chat`, `gateway`, `kanban`, `model`, `profile`, `status`, `config`, `sessions`, `skills`, `plugins`, `tools`, `mcp`, `logs`, `dashboard`, `memory`, `completion`, `prompt-size`, `update`, `tui`
+3. Full escape hatch
+   - `tag hermes -- ...`
+
+This means TAG does not reimplement all of Hermes. Instead, it owns the
+installation, profile layout, patching, orchestration, and default UX, while
+still letting you reach the underlying Hermes runtime when needed.
+
+## Release Checks
+
+Before publishing, run:
+
+```bash
+pytest -q tests/test_controller.py
+python -m build
+npm pack
+tag doctor
+tag setup --json
+```

tag_agent-0.1.0/README.md

@@ -0,0 +1,199 @@
+# TAG
+
+TAG is a standalone orchestration layer on top of Hermes. It packages the work
+done in this workspace into one installable CLI with:
+
+- a bundled Hermes source snapshot for first-run provisioning
+- managed Hermes bootstrap
+- shipped Hermes TUI patching
+- a custom `tag-control` skin
+- profile-based master/worker orchestration
+- OpenRouter worker routing
+- Codex import and runtime support
+- direct execution, Kanban execution, and benchmark history
+
+## Install
+
+```bash
+pip install tag-agent
+```
+
+This installs the `tag` command.
+
+For npm:
+
+```bash
+npm install -g tag-agent
+```
+
+For pnpm:
+
+```bash
+pnpm add -g tag-agent
+```
+
+The npm package installs a thin Node launcher for `tag`. On first run it
+creates an isolated Python runtime under `~/.tag/npm-runtime/<version>`,
+installs the bundled TAG Python package there, and then executes the same TAG
+CLI. That means the npm path still requires Python `>=3.11` and `<3.14` on
+`PATH`. The launcher will probe `python3.13`, `python3.12`, `python3.11`,
+`python3`, and `python` in that order on Unix-like systems.
+
+For a build artifact install:
+
+```bash
+python -m build
+pip install dist/tag_agent-0.1.0-py3-none-any.whl
+```
+
+For an npm artifact check:
+
+```bash
+npm pack
+```
+
+## First run
+
+```bash
+tag
+```
+
+Default behavior:
+
+1. create `~/.tag/config/tag.yaml` and the benchmark suite if missing
+2. extract the bundled Hermes snapshot into `~/.tag/managed/hermes-agent-upstream` if needed
+3. create a virtualenv for Hermes
+4. install Hermes with the required extras
+5. apply the TAG TUI patch
+6. install/build the Hermes TUI workspace
+7. bootstrap the default TAG profiles
+8. launch the orchestrator TUI
+
+The same managed bootstrap now happens automatically for non-TUI commands that
+need Hermes, for example:
+
+```bash
+tag submit --task-type mixed --execution direct --prompt "Reply with exactly: smoke-ok"
+tag benchmark --profile researcher --model-ref openrouter/deepseek/deepseek-v4-flash
+tag model --profile orchestrator -- list
+```
+
+For those commands, TAG provisions Hermes on demand and skips the TUI build if
+it is not needed, so `npm` is not required just to use submit/benchmark/model
+flows.
+
+If `tag` is started from a non-interactive context, it does not try to open the
+TUI blindly. It exits with a clear message and tells you to use `tag doctor`,
+`tag setup`, or `tag tui` from a real terminal.
+
+If you want the setup step explicitly:
+
+```bash
+tag setup
+tag tui
+```
+
+## Main commands
+
+```bash
+tag
+tag setup
+tag doctor
+tag bootstrap
+tag status
+tag assignments
+tag models --profile researcher
+tag openrouter-models --profile researcher --search gemini
+tag set-model --profile reviewer --ref openrouter/deepseek/deepseek-v4-pro
+tag submit --task-type mixed --execution direct --prompt "Reply with exactly: smoke-ok"
+tag benchmark --profile researcher --model-ref openrouter/deepseek/deepseek-v4-flash
+tag runs
+tag import-codex --profile orchestrator --codex-home ~/.codex
+tag chat --profile orchestrator -- --help
+tag config --profile orchestrator -- edit
+tag gateway --profile orchestrator -- start
+tag kanban --profile orchestrator -- list
+tag sessions --profile orchestrator -- list
+tag skills --profile orchestrator -- list
+tag plugins --profile orchestrator -- list
+tag tools --profile orchestrator -- list
+tag mcp --profile orchestrator -- list
+tag logs --profile orchestrator -- --since 1h
+tag dashboard --profile orchestrator -- --status
+tag memory --profile orchestrator -- status
+tag model --profile orchestrator -- list
+tag profile -- list
+tag completion --profile orchestrator -- zsh
+tag prompt-size --profile orchestrator
+tag update
+tag hermes --profile orchestrator -- gateway start
+tag tui --profile orchestrator
+```
+
+## Persistence
+
+TAG stores its managed state under `~/.tag` by default:
+
+- `config/tag.yaml`
+- `config/benchmark-suite.yaml`
+- `managed/hermes-agent-upstream`
+- `runtime/home`
+- `runtime/tag.sqlite3`
+
+Override the root with:
+
+```bash
+export TAG_HOME=/some/other/location
+```
+
+## Notes
+
+- The managed Hermes checkout remains Hermes internally; TAG is the packaged
+  experience and command surface around it.
+- TAG does not require a preinstalled Hermes checkout. By default it provisions
+  Hermes from a bundled source snapshot and only falls back to `git clone` if
+  that snapshot is unavailable.
+- If TAG can already discover a valid local Hermes source checkout, it will
+  reuse it automatically instead of forcing a second separate install.
+- If a real Codex CLI home already exists with `auth.json`, TAG imports that
+  into the managed orchestrator profiles automatically during setup.
+- The shipped patch only touches Hermes TUI skin handling and profile-aware
+  chrome.
+- OpenRouter keys and Codex auth remain per-profile concerns.
+- TAG currently targets Python `>=3.11` and `<3.14` and expects `npm` for full first-run
+  bootstrap because Hermes' TUI workspace is built locally. `git` is still
+  recommended for Hermes features like worktrees and for refresh/update flows,
+  but it is no longer required for the default bundled install path.
+- `tag update` is lifecycle-aware:
+  - on a bundled Hermes checkout, it refreshes the managed runtime from the
+    packaged snapshot and rebuilds it
+  - on a git-backed checkout, it delegates to Hermes' own update flow
+- The npm distribution is a launcher wrapper around the Python package, not a
+  separate Node reimplementation.
+
+## Command strategy
+
+TAG currently has three layers of command surface:
+
+1. Native TAG orchestration commands
+   - `setup`, `doctor`, `bootstrap`, `route`, `submit`, `benchmark`, `runs`
+2. High-value managed Hermes wrappers
+   - `chat`, `gateway`, `kanban`, `model`, `profile`, `status`, `config`, `sessions`, `skills`, `plugins`, `tools`, `mcp`, `logs`, `dashboard`, `memory`, `completion`, `prompt-size`, `update`, `tui`
+3. Full escape hatch
+   - `tag hermes -- ...`
+
+This means TAG does not reimplement all of Hermes. Instead, it owns the
+installation, profile layout, patching, orchestration, and default UX, while
+still letting you reach the underlying Hermes runtime when needed.
+
+## Release Checks
+
+Before publishing, run:
+
+```bash
+pytest -q tests/test_controller.py
+python -m build
+npm pack
+tag doctor
+tag setup --json
+```

tag_agent-0.1.0/TODO.md

@@ -0,0 +1,48 @@
+# TAG Todo
+
+This file tracks the remaining work needed before TAG can reasonably be
+described as a polished standalone product instead of a strong prototype.
+
+## In Progress
+
+- [ ] None
+
+## Pending
+
+- [ ] None
+
+## Completed
+
+- [x] Harden packaging and distribution
+  - add package metadata suitable for publication
+  - include shipped resources and license in sdist/wheel builds
+  - verify non-editable wheel install behavior
+  - clean generated artifacts from the source tree
+
+- [x] Re-run regression testing across all maintained surfaces
+  - TAG unit tests
+  - hermes-lab unit tests
+  - Hermes patched TUI tests/build
+  - installed `tag` smoke tests
+
+- [x] Harden bare `tag` startup behavior
+  - add TTY detection
+  - add a non-interactive fallback mode
+  - avoid hanging when launched from non-interactive contexts
+
+- [x] Improve `doctor` and `setup` prerequisite validation
+  - verify `git`, `npm`, and usable Python tooling up front
+  - surface missing dependencies before setup begins
+  - report whether Hermes checkout, patch state, and TUI build state are healthy
+
+- [x] Clarify and strengthen TAG command-surface coverage
+  - decide which Hermes capabilities should remain passthrough-only
+  - document the intended contract of `tag hermes`
+  - add any missing high-value first-class TAG commands
+
+- [x] Standalone `tag` Python package skeleton
+- [x] Managed Hermes bootstrap flow
+- [x] TAG config and benchmark suite persistence
+- [x] Shipped `tag-control` skin
+- [x] Hermes TUI patch integration
+- [x] Profile bootstrap and rendered config installation

tag_agent-0.1.0/pyproject.toml

@@ -0,0 +1,62 @@
+[build-system]
+requires = ["setuptools>=69", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "tag-agent"
+version = "0.1.0"
+description = "TAG: a Hermes-based orchestration layer with patched TUI, profile routing, and OpenRouter/Codex workflows."
+readme = "README.md"
+requires-python = ">=3.11,<3.14"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+  { name = "TAG" }
+]
+keywords = ["agents", "cli", "codex", "hermes", "openrouter", "orchestration", "tui"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development",
+  "Topic :: Terminals",
+]
+dependencies = [
+  "PyYAML>=6.0"
+]
+
+[project.optional-dependencies]
+dev = [
+  "build>=1.2.2",
+  "pytest>=8.0",
+  "twine>=6.1.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/sanskarpan/tag-agent"
+Repository = "https://github.com/sanskarpan/tag-agent.git"
+Issues = "https://github.com/sanskarpan/tag-agent/issues"
+
+[project.scripts]
+tag = "tag.controller:main"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+include-package-data = true
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+tag = [
+  "assets/skins/*.yaml",
+  "config/*.yaml",
+  "docs/*.md",
+  "patches/*.patch",
+  "vendor/*.tar.gz",
+]

tag_agent-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

tag_agent-0.1.0/src/tag/__init__.py

@@ -0,0 +1,5 @@
+"""TAG package."""
+
+__all__ = ["__version__"]
+
+__version__ = "0.1.0"

tag_agent-0.1.0/src/tag/__main__.py

@@ -0,0 +1,7 @@
+from __future__ import annotations
+
+from .cli import main
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

tag_agent-0.1.0/src/tag/assets/skins/tag-control.yaml

@@ -0,0 +1,61 @@
+name: tag-control
+description: TAG control-room skin with indigo panels, cobalt prompts, and electric-blue accents.
+colors:
+  banner_border: "#44517A"
+  banner_title: "#8FA8FF"
+  banner_accent: "#52B6FF"
+  banner_dim: "#7587B3"
+  banner_text: "#E6EEFF"
+  ui_primary: "#8FA8FF"
+  ui_accent: "#52B6FF"
+  ui_border: "#44517A"
+  ui_text: "#E6EEFF"
+  ui_muted: "#7587B3"
+  ui_label: "#B7C7FF"
+  ui_ok: "#66D7A1"
+  ui_error: "#FF7D97"
+  ui_warn: "#7FD7FF"
+  prompt: "#8FA8FF"
+  input_rule: "#44517A"
+  response_border: "#52B6FF"
+  status_bar_bg: "#0D1324"
+  status_bar_text: "#DCE6FF"
+  status_bar_strong: "#52B6FF"
+  status_bar_dim: "#7587B3"
+  status_bar_good: "#66D7A1"
+  status_bar_warn: "#7FD7FF"
+  status_bar_bad: "#A88BFF"
+  status_bar_critical: "#FF7D97"
+  session_label: "#B7C7FF"
+  session_border: "#7587B3"
+  selection_bg: "#1D294A"
+  completion_menu_bg: "#0D1324"
+  completion_menu_current_bg: "#1D294A"
+  completion_menu_meta_bg: "#0A1020"
+  completion_menu_meta_current_bg: "#16254A"
+  shell_dollar: "#52B6FF"
+branding:
+  agent_name: "TAG Control"
+  agent_icon: "◈"
+  welcome: "TAG control plane online. Type your message or /help."
+  goodbye: "TAG control plane offline."
+  response_label: " ◈ TAG "
+  prompt_symbol: "›"
+  help_header: "[tag] Commands"
+tool_prefix: "│"
+banner_logo: |
+  [bold #52B6FF]████████╗ █████╗  ██████╗[/]
+  [bold #8FA8FF]╚══██╔══╝██╔══██╗██╔════╝[/]
+  [bold #B7C7FF]   ██║   ███████║██║  ███╗[/]
+  [bold #A88BFF]   ██║   ██╔══██║██║   ██║[/]
+  [bold #7FD7FF]   ██║   ██║  ██║╚██████╔╝[/]
+banner_hero: |
+  [#52B6FF]      ╭────────────╮[/]
+  [#8FA8FF]  ╭───┤ TAG        ├───╮[/]
+  [#7587B3]  │   ╰────┬───────╯   │[/]
+  [#B7C7FF]  │   ╭────┴────╮      │[/]
+  [#52B6FF]  ├───┤ CONTROL ├───┬──┤[/]
+  [#7587B3]  │   ╰────┬────╯   │  │[/]
+  [#A88BFF]  │   ╭────┴────╮   │  │[/]
+  [#66D7A1]  ╰───┤ AGENTS  ├───╯  │[/]
+  [#7587B3]      ╰─────────╯      │[/]

tag_agent-0.1.0/src/tag/cli.py

@@ -0,0 +1,7 @@
+from __future__ import annotations
+
+from .controller import main
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

tag_agent-0.1.0/src/tag/config/benchmark-suite.yaml

@@ -0,0 +1,14 @@
+cases:
+  - id: exact-echo
+    prompt: "Reply with exactly: bench-ok"
+    expected_exact: bench-ok
+
+  - id: math-json
+    prompt: 'Return only compact JSON {"status":"ok","sum":42}'
+    expected_json:
+      status: ok
+      sum: 42
+
+  - id: bullet-format
+    prompt: "Reply with exactly these two lines and nothing else: - alpha\n- beta"
+    expected_regex: '(^|\n)- alpha\n- beta\s*$'