LogNexus
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lognexus_statusB | Inspect the current Git branch, whether the directory is a Git repository, the active issue, the routing mode and the recommended model tier. |
| lognexus_state_getA | Return the persistent LogNexus agent state (.lognexus/state.json): active issue, current subtask, completed subtasks and last synchronization timestamp. |
| lognexus_state_syncB | Synchronize the persistent state from the current Git branch and GitHub metadata, then return the updated state. |
| lognexus_state_set_taskA | Mark a subtask as in progress (equivalent to 'lognexus state set-task [title]') and return the updated state. |
| lognexus_state_finish_taskB | Mark a subtask as completed (equivalent to 'lognexus state finish-task ') and return the updated state. |
| lognexus_state_clearB | Reset the persistent LogNexus agent state to empty (equivalent to 'lognexus state clear'). |
| lognexus_commitB | Atomically create a Git commit with conventional commit format, authorship trailers, subtask file contract validation, automatic task finishing, and Git Note attachment in a single operation. |
| lognexus_note_showA | Read the LogNexus Git Note (refs/notes/lognexus) attached to a commit and return its parsed JSON payload. Defaults to HEAD. |
| lognexus_note_attachA | Attach the current LogNexus state as a Git Note (refs/notes/lognexus) to a commit. Defaults to HEAD. |
| lognexus_timelineB | Reconstruct the branch Journey Timeline against a base branch: commit list enriched with Git Notes, subtask IDs, tiers and Authored-by/Reviewed-by trailers, rendered as a Markdown table, JSON or a PR body draft. |
| lognexus_auditB | Audit the branch commits against the LogNexus review gate: commit format, Authored-by trailer, Git Note presence, subtask file contracts and reviewer/author separation. |
| lognexus_telemetryB | Inspect telemetry status, enable local or anonymous community telemetry, disable tracking, inspect zero-PII payload, generate telemetry markdown reports, or clear metrics store. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| lognexus-plan | Break a LogNexus issue down into ordered, verifiable subtasks with strict closed-delegation contracts delegated to the appropriate model tier. |
| lognexus-review | Audit a diff or pull request against the LogNexus review gate before merging into main: contracts, verification, traceability and cross-model attribution. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| LogNexus agent state | Persistent LogNexus agent state (.lognexus/state.json): active issue, current subtask, completed subtasks and last synchronization timestamp. |
| Model-tier routing configuration | Multi-model routing rules from .lognexus/routing.md, or the default tier taxonomy when the project has not been initialized. |
TDQS
Scored across 12 tools
Most tools map to a clearly distinct resource+action (state get/clear/sync, note show/attach, commit, audit, timeline, telemetry). Two mild overlaps exist: lognexus_state_get vs lognexus_state_sync (both return updated state, differing only in whether they re-read Git/GitHub) and lognexus_commit vs lognexus_note_attach, since commit already attaches a Git Note automatically.
All twelve names share the lognexus_ prefix and snake_case, with a predictable <namespace>_<action> pattern for state_* and note_* families. Minor deviation: commit, status, timeline, audit and telemetry are flat prefix+noun/verb without a resource namespace, which is a small inconsistency rather than a readability problem.
Twelve tools sit squarely in the well-scoped 3-15 range. Each one maps to a concrete workflow step (read/reset/sync state, task transitions, notes, commit, audit, timeline, telemetry) with no visible filler.
The state lifecycle (get, sync, set-task, finish-task, clear), note lifecycle (show/attach) and commit/audit/timeline reporting are covered, so core workflows have no dead ends. Gaps remain around assigning the active issue explicitly, recording a Reviewed-by trailer (audited but never written), and detaching a stale note — all workable around via raw git.