wassname/HumanAgent-MCP
1
0
Fork 0
mirror of https://github.com/wassname/HumanAgent-MCP.git synced 2026-09-09 11:14:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add GitHub Actions workflow for automated publishing and clean up unnecessary files

Browse Source
This commit is contained in:
B Harper
2025-10-26 18:14:13 +11:00
parent 347485a822
commit 464f4e0bf4
8 changed files with 2 additions and 169 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.DS_Store
Vendored
BIN
View File
Binary file not shown.
.gitignore
+2
View File
@@ -21,3 +21,5 @@ Thumbs.db
# Logs
*.log
# macOS files
.DS_Store
CHANGELOG.md
-9
View File
@@ -1,9 +0,0 @@
# Change Log
All notable changes to the "humanagent-mcp" extension will be documented in this file.
Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
## [Unreleased]
- Initial release
ToDo.md
-17
View File
@@ -1,17 +0,0 @@
[X] Assess / Set logging path and details correctly for release & dev.
[X] Create a new readme - Created truthful README.md for users and ReadMeDev.md for developers
[X] Consider how updates to the extension will work.
[X] Override Prompt Script is not generated from exact coded system tool description - seems to be stale - where is the info coming from for the override creation?
[X] Can we include an option to enable logging and set logging to take place in the .vscode directory of the active workspace. It should be an option that the user can turn on in the cog. And should be off by default.
[X] There should be an SSE sent to website when chat is named to force it to update the name.
[X] Consider reminding AI to allways use this method for replies in each response unless some keyword is included - we can add this to the outgoing chat messages and just strip it from what we show in the chat log?
[X] We should look for and exlude and tool named "example_custom_tool" from the /tools endpoint as it should not be advertised as a real tool to the AI
[X] The updates / overrides seem to be advertised @ /tools though the Configure tools screen on vs code doesnt show that the new description.
[X] The message formatting from the ai, cariagge returns etc are not observed by the website - its just a big string in one paragraph. Can we fix this? AI message formatting looks fine in vscode interface. WEB INTERFACE STILL SHOWS EVERYTHING ON ONE LINE.
[X] When sending a message from VS code it looses some history of the chat - seems to keep its own messages but looses old ai agent messages and any from the web client.
[ ] Consider how a user might also interact from their mobile phone. Dont want to do port forwarding and setting up web servers etc. How about using telegram as an interface - could this work? Look into it.
[ ] Would be great if I could paste in an image or screen shot - Copilot agent allows this in the vscode plugin.
[X] put an option in the MCP.json and the global setup to change the default timout to a new value - FIXED: Removed silent 300-second fallback, now waits indefinitely if no timeout specified, or uses explicit timeout from tool params/overrides
[X] Getting chat friendly name on startup seems to be failing "[Extension Host] Failed to restore session name: TypeError: fetch failed (at console.<anonymous> (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:203:32117))" - FIXED: Moved session name restoration to after server startup with retry logic
[X] Package Extension so we can install locally and test the seperation of workspaces - to ensure we do not cross contaminate anything between workspaces.
[X] Publish Extension - WHEN ALL ELSE IS DONE!
response-debug.txt
-54
View File
@@ -1,54 +0,0 @@
2025-10-24T08:06:36.164Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761293186207
2025-10-24T08:25:56.900Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761294344871
2025-10-24T09:32:10.933Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761298318952
2025-10-24T09:32:25.510Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761298337616
2025-10-24T09:33:01.254Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761298351000
2025-10-24T09:33:44.808Z - RESPONSE ENDPOINT CALLED - RequestID: 8-1761298414137
2025-10-24T09:36:01.128Z - RESPONSE ENDPOINT CALLED - RequestID: 10-1761298555386
2025-10-24T09:36:37.205Z - RESPONSE ENDPOINT CALLED - RequestID: 11-1761298573778
2025-10-25T00:51:00.473Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761353445662
2025-10-25T04:01:02.918Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761364822234
2025-10-25T04:15:25.912Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761365673152
2025-10-25T05:11:52.195Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761369085275
2025-10-25T05:13:08.587Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761369125738
2025-10-25T05:13:46.757Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761369196447
2025-10-25T05:14:13.224Z - RESPONSE ENDPOINT CALLED - RequestID: 6-1761369242206
2025-10-25T05:14:37.881Z - RESPONSE ENDPOINT CALLED - RequestID: 7-1761369262103
2025-10-25T05:15:07.921Z - RESPONSE ENDPOINT CALLED - RequestID: 8-1761369292715
2025-10-25T05:16:21.162Z - RESPONSE ENDPOINT CALLED - RequestID: 9-1761369320152
2025-10-25T05:16:54.687Z - RESPONSE ENDPOINT CALLED - RequestID: 10-1761369392733
2025-10-25T05:18:12.537Z - RESPONSE ENDPOINT CALLED - RequestID: 11-1761369434229
2025-10-25T05:31:53.635Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761370255763
2025-10-25T22:25:03.252Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761430956625
2025-10-25T23:25:06.434Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761433618081
2025-10-25T23:51:51.036Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761436271152
2025-10-26T00:10:24.529Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761437390231
2025-10-26T00:50:40.987Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761439764111
2025-10-26T02:36:30.812Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761446137388
2025-10-26T02:36:46.213Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761446194329
2025-10-26T02:37:06.823Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761446210035
2025-10-26T02:39:35.845Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761446268480
2025-10-26T02:52:49.230Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761447129937
2025-10-26T02:58:10.739Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761447173815
2025-10-26T02:58:23.071Z - RESPONSE ENDPOINT CALLED - RequestID: 6-1761446231600
2025-10-26T03:12:51.723Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761448352577
2025-10-26T03:13:06.068Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761448377257
2025-10-26T03:14:30.027Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761448389577
2025-10-26T03:27:07.019Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761449187260
2025-10-26T03:28:01.453Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761449230412
2025-10-26T04:12:40.297Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761451913551
2025-10-26T04:32:38.258Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761453136803
2025-10-26T04:33:24.748Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761453160409
2025-10-26T04:34:19.385Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761453244838
2025-10-26T04:34:47.275Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761453207008
2025-10-26T04:35:07.379Z - RESPONSE ENDPOINT CALLED - RequestID: 6-1761453290240
2025-10-26T04:35:22.313Z - RESPONSE ENDPOINT CALLED - RequestID: 7-1761453309691
2025-10-26T04:35:24.503Z - RESPONSE ENDPOINT CALLED - RequestID: 8-1761453324492
2025-10-26T04:35:34.152Z - RESPONSE ENDPOINT CALLED - RequestID: 9-1761453327469
2025-10-26T04:35:59.241Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761453262457
2025-10-26T04:37:02.349Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761453363480
2025-10-26T04:37:38.418Z - RESPONSE ENDPOINT CALLED - RequestID: 10-1761453337063
2025-10-26T04:58:25.162Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761454660214
2025-10-26T04:59:00.155Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761454713902
2025-10-26T06:02:38.643Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761458547802
2025-10-26T06:03:35.106Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761458605115
src/.DS_Store
Vendored
BIN
View File
Binary file not shown.
test-port.js
-41
View File
@@ -1,41 +0,0 @@
const net = require('net');
const http = require('http');
async function isPortInUseNet(port) {
return new Promise((resolve) => {
const server = net.createServer();
server.listen(port, '127.0.0.1', () => {
console.log(`NET: Port ${port} available - server created successfully`);
server.close(() => resolve(false)); // Port is available
});
server.on('error', (err) => {
console.log(`NET: Port ${port} in use - error: ${err.message}`);
resolve(true); // Port is in use
});
});
}
async function isPortInUseHttp(port) {
return new Promise((resolve) => {
const server = http.createServer();
server.listen(port, '127.0.0.1', () => {
console.log(`HTTP: Port ${port} available - server created successfully`);
server.close(() => resolve(false)); // Port is available
});
server.on('error', (err) => {
console.log(`HTTP: Port ${port} in use - error: ${err.message}`);
resolve(true); // Port is in use
});
});
}
console.log('Testing port 3737...');
Promise.all([isPortInUseNet(3737), isPortInUseHttp(3737)]).then(([netResult, httpResult]) => {
console.log(`NET result - Port 3737 in use: ${netResult}`);
console.log(`HTTP result - Port 3737 in use: ${httpResult}`);
process.exit(0);
});
vsc-extension-quickstart.md
-48
View File
@@ -1,48 +0,0 @@
# Welcome to your VS Code Extension
## What's in the folder
* This folder contains all of the files necessary for your extension.
* `package.json` - this is the manifest file in which you declare your extension and command.
* The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
* `src/extension.ts` - this is the main file where you will provide the implementation of your command.
* The file exports one function, `activate`, which is called the very first time your extension is activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
* We pass the function containing the implementation of the command as the second parameter to `registerCommand`.
## Setup
* install the recommended extensions (amodio.tsl-problem-matcher, ms-vscode.extension-test-runner, and dbaeumer.vscode-eslint)
## Get up and running straight away
* Press `F5` to open a new window with your extension loaded.
* Run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`.
* Set breakpoints in your code inside `src/extension.ts` to debug your extension.
* Find output from your extension in the debug console.
## Make changes
* You can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`.
* You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.
## Explore the API
* You can open the full set of our API when you open the file `node_modules/@types/vscode/index.d.ts`.
## Run tests
* Install the [Extension Test Runner](https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
* Run the "watch" task via the **Tasks: Run Task** command. Make sure this is running, or tests might not be discovered.
* Open the Testing view from the activity bar and click the Run Test" button, or use the hotkey `Ctrl/Cmd + ; A`
* See the output of the test result in the Test Results view.
* Make changes to `src/test/extension.test.ts` or create new test files inside the `test` folder.
* The provided test runner will only consider files matching the name pattern `**.test.ts`.
* You can create folders inside the `test` folder to structure your tests any way you want.
## Go further
* Reduce the extension size and improve the startup time by [bundling your extension](https://code.visualstudio.com/api/working-with-extensions/bundling-extension).
* [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VS Code extension marketplace.
* Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).