gaunt-sloth-assistant 1.4.1 → 1.5.0

package/README.md

@@ -1,358 +1,51 @@
-# Gaunt Sloth Assistant
-[![Tests and Lint](https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/actions/workflows/unit-tests.yml/badge.svg)](https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/actions/workflows/unit-tests.yml) [![Integration Tests](https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/actions/workflows/integration-tests.yml/badge.svg?event=push)](https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/actions/workflows/integration-tests.yml)
+# gaunt-sloth-assistant
 
-Gaunt Sloth Assistant is a command-line AI assistant for CI/CD workflows, code reviews, and DIY projects. It supports PR and diff reviews with requirements context, code and diff Q&A, interactive chat and coding sessions, and controlled automation through predefined tools and JSON or JavaScript configuration.
+The main CLI application for Gaunt Sloth.
 
-![GSloth Banner](assets/gaunt-sloth-logo.png)
+## Contents
 
-Based on [LangChain.js](https://github.com/langchain-ai/langchainjs)
+- CLI entry point and commander-based command registration
+- Commands: `ask`, `review`, `pr`, `chat`, `code`, `init`, `get`, `api`
+- Command utilities and config setup
+- Vendor package wiring (all LangChain provider packages)
+- Integration tests
 
-[Documentation](https://gaunt-sloth-assistant.github.io/docs/) | [Official Site](https://gaunt-sloth-assistant.github.io/) | [NPM](https://www.npmjs.com/package/gaunt-sloth-assistant) | [GitHub](https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant)
+## CLI Binaries
 
-## Why?
+The package registers four equivalent binary aliases:
 
-Gaunt Sloth's promise is that it is small, extendable, cross-platform and can itself be a dependency in your project.
+- `gaunt-sloth-assistant`
+- `gaunt-sloth`
+- `gsloth`
+- `gth`
 
-The GSloth was initially built as a code review tool, fetching PR contents and Jira contents before feeding them to
-the LLM, but we ourselves found many more use cases which we initially did not anticipate; for example,
-we may have it as a dependency in an MCP project, allowing us to quickly spin it up to simulate or test some use cases.
+## Dependencies
 
-The promise of Gaunt Sloth:
+- `@gaunt-sloth/core`
+- `@gaunt-sloth/tools`
+- `@gaunt-sloth/api`
+- `@gaunt-sloth/review`
+- `commander`
+- All LangChain vendor packages (anthropic, google-genai, groq, openai, vertexai, xai, etc.)
 
-- **Minimum dependencies**. Ideally, we aim to only have CommanderJS and some packages from LangChainJS and LangGraphJS.
-- **Extensibility**. Feel free to write some JS and create your Tool, Provider or connect to the MCP server of your choice.
-- **No vendor lock-in**. Just BYO API keys.
-- **Easy installation via NPM**.
-- **All prompts are editable** via markdown files. 
+This is the only package in the workspace that pulls in AI vendor dependencies directly. All other packages treat vendors as optional peers.
 
-## What GSloth does
+## Re-exports
 
-Unlike autonomous coding agents or hosted review services, GSloth is a **configuration-driven CLI tool** that you wire into your own workflows and pipelines. You choose the model, the provider, the prompts, and the tools — GSloth orchestrates them.
-
-**Controlled automation**
-- Define custom shell tools (deployments, migrations, test runs) in JSON config with parameter validation
-- Connect to MCP servers, including remote servers with OAuth
-- Communicate with external AI agents via the A2A protocol
-
-**Model experimentation**
-- Swap models and providers through config — no code changes needed
-- Works with Anthropic, Google (Vertex AI, AI Studio), OpenAI, Groq, DeepSeek, xAI, OpenRouter, local models (LM Studio, Ollama), and any LangChain-compatible provider
-- Customizable middleware pipeline (prompt caching, summarization, or your own)
-- All system prompts are editable markdown files
-
-**Code reviews and PR workflows**
-- Review PRs with requirement context pulled from GitHub issues or Jira (`gsloth pr 42 12`)
-- Review local diffs before committing (`git --no-pager diff | gsloth review`)
-- Run automated reviews in CI/CD — post results as PR comments via GitHub Actions
-
-**Q&A, chat, and coding sessions**
-- Ask questions about specific files (`gsloth ask "explain this" -f utils.js`)
-- Interactive chat and coding sessions with filesystem access
-
-**Output handling**
-- Saves all responses to timestamped files (override with `-w/--write-output-to-file`)
-- Materializes binary model outputs (e.g. generated images) as local files
-
-### To make GSloth work, you need an **API key** from some AI provider, such as:
-
-- OpenRouter
-- Groq;
-- DeepSeek;
-- Google AI Studio and Google Vertex AI;
-- Anthropic;
-- OpenAI (and other providers using OpenAI format, such as Inception);
-- Local AI: LM Studio, Ollama, llama.cpp (Via OpenAI compatibitlity)
-- Ollama with JS config (some of the models, see https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/discussions/107)
-- xAI;
-
-`*` Any other provider supported by LangChain.JS should also work with [JS config](./docs/CONFIGURATION.md#javascript-configuration).
-
-## Commands Overview
-
-`gth` and `gsloth` commands are used interchangeably, both `gsloth pr 42` and `gth pr 42` do the same thing.
-
-For detailed information about all commands, see [docs/COMMANDS.md](./docs/COMMANDS.md).
-
-### Global Flags
-
-These apply to every command:
-- `--config <path>` – load a specific config file without moving directories
-- `-i, --identity-profile <name>` – switch to another profile under `.gsloth/.gsloth-settings/<name>/`
-- `-w, --write-output-to-file <value>` – control response files (`true` by default, use `-wn`/`-w0` for false, or pass a filename)
-- `--verbose` – enable verbose LangChain/LangGraph logs (useful when debugging prompts)
-
-### Available Commands:
-
-- **`init`** - Initialize Gaunt Sloth in your project (auto-detects API keys when called without arguments)
-- **`get`** - Inspect the effective prompt or provider-backed input used by another command
-- **`pr`** - ⚠️ This feature requires GitHub CLI to be installed. Review pull requests with optional requirement integration (GitHub issues or Jira).
-- **`review`** - Review any diff or content from various sources
-- **`ask`** - Ask questions about code or programming topics
-- **`chat`** - Start an interactive chat session
-- **`code`** - Write code interactively with full project context
-
-### Quick Examples:
-
-**Initialize project:**
-```bash
-gsloth init              # Auto-detect API keys and select provider
-gsloth init anthropic    # Or specify provider directly
-```
-
-**Review PR with requirements:**
-```bash
-gsloth pr 42 23  # Review PR #42 with GitHub issue #23
-```
-
-**Inspect command inputs:**
-```bash
-gsloth get pr prompt
-gsloth get pr content 42
-gsloth get review requirements PROJ-123
-```
-
-**Review local changes:**
-```bash
-git --no-pager diff | gsloth review
-```
-
-**Review changes between a specific tag and the HEAD:**
-```bash
-git --no-pager diff v0.8.3..HEAD | gth review
-```
-
-**Review diff between head and previous release and head using a specific requirements provider (GitHub issue 38), not the one which is configured by default:
-```bash
-git --no-pager diff v0.8.10 HEAD | npx gth review --requirements-provider github -r 38
-```
-
-**Ask questions:**
-```bash
-gsloth ask "What does this function do?" -f utils.js
-```
-
-**Write release notes:**
-```bash
-git --no-pager diff v0.8.3..HEAD | gth ask "inspect existing release notes in release-notes/v0_8_2.md; inspect provided diff and write release notes to v0_8_4.md"
-```
-
-To write this to filesystem, you'd need to add filesystem access to the *ask* command in `.gsloth.config.json`.
-
-```json
-{"llm": {"type": "vertexai", "model": "gemini-2.5-pro"}, "commands": {"ask": {"filesystem": "all"}}}
-```
-
-*You can improve this significantly by modifying project guidelines in `.gsloth.guidelines.md` or maybe with keeping instructions in file and feeding it in with `-f`.
-
-
-**Interactive sessions:**
-```bash
-gsloth chat  # Start chat session
-gsloth code  # Start coding session
-```
-Running `gsloth` with no subcommand also drops you into `chat`.
+`gaunt-sloth-assistant` re-exports public APIs from the sub-packages for backward compatibility. Consumers that previously imported directly from `gaunt-sloth-assistant` continue to work without changes.
 
 ## Installation
 
-Tested with Node 24 LTS.
-
-### NPM
 ```bash
-npm install gaunt-sloth-assistant -g
-```
-
-## Configuration
-
-> Gaunt Sloth currently only functions from the directory which has a configuration file (`.gsloth.config.js`, `.gsloth.config.json`, or `.gsloth.config.mjs`) and `.gsloth.guidelines.md`. Configuration files can be located in the project root or in the `.gsloth/.gsloth-settings/` directory.
->
-> You can also specify a path to a configuration file directly using the `-c` or `--config` global flag, for example `gth -c /path/to/your/config.json ask "who are you?"`
-> Note, however, is that project guidelines are going to be used from current directory if they exist and simple install dir prompt is going to be used if nothing found.
-
-Configuration can be created with `gsloth init [vendor]` command.
-Currently, openrouter, anthropic, groq, deepseek, openai, google-genai, vertexai and xai can be configured with `gsloth init [vendor]`.
-For OpenAI-compatible providers like Inception, use `gsloth init openai` and modify the configuration.
-
-More detailed information on configuration can be found in [CONFIGURATION.md](./docs/CONFIGURATION.md)
-
-Gaunt Sloth also supports `.aiignore` for excluding files from filesystem tools, with overrides via config.
-
-### Custom Tools
-
-Gaunt Sloth supports defining custom shell commands that the AI can execute. These custom tools:
-- Work across all commands (`pr`, `review`, `code`, `ask`, `chat`)
-- Can be configured globally or per-command
-- Support parameters with security validation
-- Are useful for deployments, migrations, automation, and more
-
-**Example configuration:**
-```json
-{
-  "llm": {"type": "vertexai", "model": "gemini-2.5-pro"},
-  "customTools": {
-    "deploy": {
-      "command": "npm run deploy",
-      "description": "Deploy the application"
-    },
-    "run_migration": {
-      "command": "npm run migrate -- ${name}",
-      "description": "Run a database migration",
-      "parameters": {
-        "name": {"description": "Migration name"}
-      }
-    }
-  }
-}
+npm install -g gaunt-sloth-assistant
 ```
 
-See [Custom Tools Configuration](./docs/CONFIGURATION.md#custom-tools-configuration) for complete documentation.
-
-### Google GenAI (AI Studio)
-
-```bash
-cd ./your-project
-gsloth init google-genai
-```
-Make sure you either define `GOOGLE_API_KEY` environment variable or edit your configuration file and set up your key.
-It is recommended to obtain API key from Google AI Studio official website rather than from a reseller.
-
-### Google Vertex AI
-
-```bash
-cd ./your-project
-gsloth init vertexai
-gcloud auth login
-gcloud auth application-default login
-```
-
-As of 19 Nov 2025, Gemini 3 on Vertex AI works with `global` and `us-central1` locations when using the default `aiplatform.googleapis.com` endpoint.
-However, regional endpoints (e.g., `us-central-aiplatform.googleapis.com`) currently return 404 for Gemini 3.
-Example config:
-```json
-{
-  "llm": {
-    "type": "vertexai",
-    "model": "gemini-3-pro-preview",
-    "location": "global"
-  }
-}
-```
-
-### Open Router
-
-```bash
-cd ./your-project
-gsloth init openrouter
-```
-
-Make sure you either define `OPEN_ROUTER_API_KEY` environment variable or edit your configuration file and set up your key.
-
-### Anthropic
-
-```bash
-cd ./your-project
-gsloth init anthropic
-```
-
-Make sure you either define `ANTHROPIC_API_KEY` environment variable or edit your configuration file and set up your key.
-
-### Groq
-```bash
-cd ./your-project
-gsloth init groq
-```
-Make sure you either define `GROQ_API_KEY` environment variable or edit your configuration file and set up your key.
-
-### DeepSeek
-```bash
-cd ./your-project
-gsloth init deepseek
-```
-Make sure you either define `DEEPSEEK_API_KEY` environment variable or edit your configuration file and set up your key.
-It is recommended to obtain API key from DeepSeek official website rather than from a reseller.
-
-### OpenAI
-```bash
-cd ./your-project
-gsloth init openai
-```
-Make sure you either define `OPENAI_API_KEY` environment variable or edit your configuration file and set up your key.
-
-### LM Studio
-LM Studio provides a local OpenAI-compatible server for running models on your machine:
-```bash
-cd ./your-project
-gsloth init openai
-```
-Then edit your configuration file to point to LM Studio (default: `http://127.0.0.1:1234/v1`).
-Use any string for the API key (e.g., `"none"`) - LM Studio doesn't validate it.
-
-**Important:** The model must support tool calling. Tested models include gpt-oss, granite, nemotron, seed, and qwen3.
-
-See [CONFIGURATION.md](./docs/CONFIGURATION.md#lm-studio) for detailed setup.
-
-### OpenAI-compatible providers (Inception, etc.)
-For providers using OpenAI-compatible APIs:
-```bash
-cd ./your-project
-gsloth init openai
-```
-Then edit your configuration to add custom base URL and API key. See [CONFIGURATION.md](./docs/CONFIGURATION.md) for examples.
-
-### xAI
-```bash
-cd ./your-project
-gsloth init xai
-```
-Make sure you either define `XAI_API_KEY` environment variable or edit your configuration file and set up your key.
-
-### Other AI providers
-Any other AI provider supported by Langchain.js can be configured with js [Config](./docs/CONFIGURATION.md).
-For example, Ollama can be set up with JS config (some of the models, see https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/discussions/107)
-
-### JavaScript Configuration with Custom Middleware and Tools
-JavaScript configs enable advanced customization including custom middleware and tools that aren't available in JSON configs. See the [JavaScript config example](./examples/js-config/README.md) for a complete demonstration of creating custom logging middleware and custom tools.
-
-## Integration with GitHub Workflows / Actions
-
-Example GitHub workflows integration can be found in [.github/workflows/review.yml;](.github/workflows/review.yml)
-this example workflow performs AI review on any pushes to Pull Request, resulting in a comment left by,
-GitHub actions bot.
-
-## MCP (Model Context Protocol) Servers
-
-Gaunt Sloth supports connecting to MCP servers, including those requiring OAuth authentication.
-
-This has been tested with the Atlassian Jira MCP server.
-See the [MCP configuration section](./docs/CONFIGURATION.md#model-context-protocol-mcp) for detailed setup instructions, or the [Jira MCP example](./examples/jira-mcp) for a working configuration.
-
-If you experience issues with the MCP auth try finding `.gsloth` dir in your home directory,
-and delete JSON file matching the server you are trying to connect to,
-for example for atlassian MCP the file would be `~/.gsloth/.gsloth-auth/mcp.atlassian.com_v1_sse.json`
-
-## A2A (Agent-to-Agent) Protocol Support (Experimental)
-
-Gaunt Sloth supports the [A2A protocol](https://a2a-protocol.org/) for connecting to external AI agents. See [CONFIGURATION.md](./docs/CONFIGURATION.md#a2a-agent-to-agent-protocol-support-experimental) for setup instructions.
-
-## Uninstall
-Uninstall global NPM package:
-```bash
-npm uninstall -g gaunt-sloth-assistant
-```
-
-Remove global config (if any)
-```bash
-rm -r ~/.gsloth
-```
-
-Remove configs from project (if necessary)
-```bash
-rm -r ./.gsloth*
-```
+For full usage documentation see the [root README](../../README.md) and [docs/COMMANDS.md](../../docs/COMMANDS.md).
 
-## Contributing
-Contributions are welcome through GitHub Issues and pull requests.
-For contributor workflow, local setup, testing expectations, and PR guidance, see [CONTRIBUTING.md](./CONTRIBUTING.md).
-Project participation is also covered by the [Code of Conduct](./CODE_OF_CONDUCT.md).
+## Related packages
 
-## License
-License is [MIT](https://opensource.org/license/mit). See [LICENSE](LICENSE)
+- [`@gaunt-sloth/core`](../core) — Core utilities, config, and agent infrastructure
+- [`@gaunt-sloth/tools`](../tools) — Built-in tools, filesystem toolkit, and middleware registry
+- [`@gaunt-sloth/api`](../api) — API server, AG-UI, MCP, and A2A integration
+- [`@gaunt-sloth/review`](../review) — Review and Q&A modules with standalone CLI
+- [`gaunt-sloth-assistant`](../assistant) — Main CLI application (this package)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gaunt-sloth-assistant",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "description": "",
   "license": "MIT",
   "author": "Andrew Kondratev",
@@ -10,6 +10,10 @@
     "type": "git",
     "url": "git+https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant.git"
   },
+  "bugs": {
+    "url": "https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant/issues"
+  },
+  "homepage": "https://github.com/Galvanized-Pukeko/gaunt-sloth-assistant#readme",
   "keywords": [
     "ai",
     "agent",
@@ -22,17 +26,7 @@
     "npm": ">=11.0.0"
   },
   "scripts": {
-    "clean": "tsc -b -clean",
-    "build": "tsc -b -clean && tsc",
-    "test": "npm run build && npx tsc -p spec/tsconfig.json --noEmit && vitest run",
-    "it": "npm run build && node it.js",
-    "it-verbose": "npm run build && GSLOTH_IT_VERBOSE=1 node it.js",
-    "lint": "eslint . --ext .js,.ts",
-    "lint-n-fix": "eslint . --ext .js,.ts --fix",
-    "format": "prettier --write 'src/**/*.{js,ts}'",
-    "prepare": "npm run build",
-    "typedoc": "typedoc",
-    "chat": "node cli.js"
+    "build": "tsc"
   },
   "bin": {
     "gaunt-sloth-assistant": "cli.js",
@@ -41,44 +35,18 @@
     "gth": "cli.js"
   },
   "dependencies": {
-    "@a2a-js/sdk": "^0.3.13",
-    "@ag-ui/core": "^0.0.47",
-    "@ag-ui/encoder": "^0.0.47",
-    "@langchain/anthropic": "^1.3.25",
-    "@langchain/core": "^1.1.35",
-    "@langchain/deepseek": "^1.0.18",
-    "@langchain/google": "^0.1.8",
-    "@langchain/groq": "^1.1.5",
-    "@langchain/langgraph": "^1.2.5",
-    "@langchain/mcp-adapters": "^1.1.3",
+    "@gaunt-sloth/api": "^0.0.3",
+    "@gaunt-sloth/core": "^0.0.4",
+    "@gaunt-sloth/review": "^0.0.4",
+    "@gaunt-sloth/tools": "^0.0.1",
+    "@langchain/anthropic": "^1.3.28",
+    "@langchain/core": "^1.1.42",
+    "@langchain/deepseek": "^1.0.25",
+    "@langchain/google": "^0.1.11",
+    "@langchain/groq": "^1.2.0",
     "@langchain/openai": "^1.2.0",
-    "@langchain/xai": "^1.3.10",
-    "@modelcontextprotocol/sdk": "^1.27.1",
-    "commander": "^14.0.3",
-    "diff": "^8.0.3",
-    "express": "^5.2.1",
-    "langchain": "^1.2.36",
-    "minimatch": "^10.2.4"
-  },
-  "devDependencies": {
-    "@eslint/js": "^10.0.1",
-    "@types/express": "^5.0.6",
-    "@types/node": "^24.12.0",
-    "@typescript-eslint/eslint-plugin": "^8.57.1",
-    "@typescript-eslint/parser": "^8.57.1",
-    "eslint": "^10.1.0",
-    "eslint-config-prettier": "^10.1.8",
-    "eslint-plugin-prettier": "^5.5.5",
-    "globals": "^17.4.0",
-    "jiti": "^2.6.1",
-    "prettier": "^3.8.1",
-    "typedoc": "^0.28.17",
-    "typescript": "^5.9.3",
-    "vitest": "^4.1.0"
-  },
-  "overrides": {
-    "rimraf": "^6.1.0",
-    "minimatch": "^10.2.4"
+    "@langchain/xai": "^1.3.17",
+    "commander": "^14.0.3"
   },
   "imports": {
     "#src/*.js": "./dist/*.js"

package/.gsloth.backstory.md

@@ -1,17 +0,0 @@
-Your name is Gaunt Sloth, a programmer with comprehensive expertise across programming languages. Maintain a
-professional, direct communication style. Begin responses with substance, not pleasantries or self-promotion.
-
-Your priority is code correctness and bug prevention over social niceties, though you remain courteous in all
-interactions. Focus on technical accuracy and practical solutions.
-
-Use visual indicators when providing feedback:
-
-- ✅ for correct implementations (and approvals)
-- ⚠️ for potential issues or areas needing attention
-- ❌ for errors or problematic approaches (and rejections)
-
-You may enhance communication with relevant emojis throughout your responses to improve clarity and readability,
-but do not include foolish smiley faces.
-
-Never include decorative emojis within code snippets — only use them in code when they're part of the actual
-logic, string literals, or were present in the original code being discussed.

package/.gsloth.chat.md

@@ -1,11 +0,0 @@
-# Chat Mode Instructions
-
-You are a helpful AI assistant engaged in a conversational chat session. Your role is to:
-
-- Provide informative, accurate, and helpful responses to user queries
-- Maintain context throughout the conversation
-- Be conversational and friendly while remaining professional
-- Ask clarifying questions when needed to better understand the user's intent
-- Provide examples and explanations when appropriate
-
-Remember that this is an interactive chat session, so keep your responses concise and engaging. Focus on being helpful while maintaining a natural conversational flow.

package/.gsloth.code.md

@@ -1,27 +0,0 @@
-# Code Mode Instructions
-
-You are an AI coding assistant with full file system access within the user's project. Your role is to:
-
-- Help write, modify, and debug code
-- Understand and work with the existing codebase
-- Follow project conventions and best practices
-- Create, read, update, and delete files as needed to complete coding tasks
-- Run commands and scripts to test and validate changes
-- Provide clear explanations of the changes you make
-
-You have access to the entire project directory and can:
-- Navigate the file system
-- Read and analyze existing code
-- Make modifications to implement features or fix bugs
-- Create new files and directories as needed
-- Execute commands to run tests, build the project or run static analysis (lint)
-
-Focus on writing clean, maintainable code that follows the project's established patterns and conventions. Always test your changes when possible and explain what you're doing and why.
-
-## Running tests
-
-- When working on functionality always prefer running a single test, over the entire suite;
-- Abstain from running tests in circles, run the test once, if it fails — inspect the output carefully and try to fix it;
-- Run full tests suite as a penultimate step, when everything is fixed, but before running the lint;
-- Run lint only as a final step when everything else is fixed;
-- If nothing seems to work, ask for user's assistance;

package/.gsloth.guidelines.md

@@ -1 +0,0 @@
-

package/.gsloth.review.md

@@ -1,15 +0,0 @@
-If requirements were provided, first check that the implemented code implements these requirements.
-Document that you checked the code to implement requirements.
-Reject the change if it appears to implement something else instead of required change.
-
-Provide specific feedback on any areas of concern or suggestions for improvement.
-Please categorize your feedback (e.g., "Bug," "Suggestion," "Nitpick").
-
-Important! In the end, conclude if you would recommend approving this PR or not.
-Use ✅⚠️❌ symbols to highlight your feedback appropriately.
-
-Finish with a short 1-2 sentence summary that captures the overall state of the review.
-
-Thank you for your thorough review!
-
-Important! You are likely to be dealing with git diff below, please don't confuse removed and added lines.

package/.gsloth.system.md

@@ -1,10 +0,0 @@
-# Filesystem Context
-
-When the user mentions directories and files without specifying an exact location, this is likely referring to files in the current working directory (`.`).
-
-For example:
-- "Read the config file" likely means a configuration file in the current directory
-- "Check the tests" likely refers to test files in the current project
-- "Look at the source code" typically means source files in the current directory structure
-
-Always consider the current working directory as the default context for file operations unless the user specifies an absolute path or different location.

package/LICENSE

@@ -1,7 +0,0 @@
-Copyright 2025-present Andrew Kondratev
-
-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.

package/dist/builtInToolsConfig.d.ts

@@ -1,31 +0,0 @@
-import { StructuredToolInterface } from '@langchain/core/tools';
-import { GthConfig } from '#src/config.js';
-import { GthCommand } from '#src/core/types.js';
-/**
- * Available built-in tools may be configured in JSON config, see `builtInTools` of {@link GthConfig}.
- *
- * Does not include `filesystem`, because filesystem has its own config in {@link GthConfig}.
- */
-export declare const AVAILABLE_BUILT_IN_TOOLS: {
-    /**
-     * Reference tool. Simply prints provided argument to the screen.
-     */
-    readonly gth_status_update: "#src/tools/gthStatusUpdateTool.js";
-    /**
-     * Tool allowing to log work against a specific Jira issue.
-     * Needs JIRA_CLOUD_ID, JIRA_USERNAME and JIRA_API_PAT_TOKEN environment variables
-     */
-    readonly gth_jira_log_work: "#src/tools/gthJiraLogWorkTool.js";
-    /**
-     * Web fetch tool.
-     */
-    readonly gth_web_fetch: "#src/tools/gthWebFetchTool.js";
-    /**
-     * A2UI Surface Tool. Allows the LLM to return A2UI JSONL payloads streamed as TOOL_CALL_ARGS events.
-     */
-    readonly show_a2ui_surface: "#src/tools/showA2UISurfaceTool.js";
-};
-/**
- * Get default tools based on filesystem and built-in tools configuration
- */
-export declare function getDefaultTools(config: GthConfig, command?: GthCommand): Promise<StructuredToolInterface[]>;