tasqmate 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +12 -4
  2. package/dist/tasqmate.js +968 -213
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -127,18 +127,25 @@ claude auth login # or: codex login, or hermes setup (you sign in; the br
127
127
  tasqmate bridge setup --map "Homepage=~/code/homepage"
128
128
  ```
129
129
 
130
- `setup` finds `claude`, `codex` and `hermes`, checks their sign-in with `claude auth status` / `codex login status` / Hermes's ACP handshake only, prints a code to approve on the pair page (an admin or the agent's owner picks the agent), keeps the agent key in the OS keychain (macOS Keychain, libsecret, Windows Credential Manager; a 0600 file when there is none), maps project folders and installs a background service (launchd, a systemd user unit, or a logon task). Claude runs through the Claude Agent SDK, which `setup` installs for the bridge alone on first use.
130
+ `setup` finds `claude`, `codex` and `hermes`, checks their sign-in with `claude auth status` / `codex login status` / Hermes's ACP handshake only, prints a code to approve on the pair page (an admin or the agent's owner picks the agent), keeps the agent key in the OS keychain (macOS Keychain, libsecret, Windows Credential Manager; a 0600 file when there is none), saves the pairing, maps project folders (`~` is your home folder; a folder that isn't there is asked for again, and stopping here keeps the pairing so `bridge map` can finish) and installs a background service (launchd, a systemd user unit, or a logon task). Claude runs through the Claude Agent SDK, which `setup` installs for the bridge alone on first use.
131
131
 
132
132
  Hermes runs as `hermes acp` (the Agent Client Protocol) with your own Hermes setup: its tools are the ones your Hermes config gives ACP. The bridge answers what Hermes asks about: a file edit is allowed only inside the mapped folder, and a command Hermes flags as needing approval is refused, because nobody is there to approve it. What Hermes does not ask about (reading files, ordinary commands, web tools you enabled) runs as it would in your editor, so pick that setup with care, or give Hermes a profile with fewer tools.
133
133
 
134
134
  | Command | What |
135
135
  | --- | --- |
136
- | `bridge setup` | Pair, map folders, install the service. `--harness claude\|codex\|hermes`, `--map project=folder` (repeat), `--no-service`, `--runs-per-hour`, `--timeout`, `--max-turns` |
136
+ | `bridge setup` | Pair, map folders, install the service. `--harness claude\|codex\|hermes`, `--map project=folder` (repeat), `--no-service`, `--runs-per-hour`, `--timeout`, `--max-turns`, `--replace` (pair again without asking when this machine is already paired), `--resume` (finish a setup that stopped after pairing) |
137
137
  | `bridge start` | Run in the foreground (what the service runs) |
138
- | `bridge status` | Agent, harness sign-in, server presence, service, folders, limits |
138
+ | `bridge status` | Agent, harness sign-in, server presence, service, folders, limits, and a Next step line when something is off |
139
+ | `bridge doctor [--fix]` | Check everything in order (CLI, pairing, key, Tasqmate, harness, service, folders) and print the fix; `--fix` applies the safe ones after asking; exits 1 when something is wrong |
139
140
  | `bridge logs [-n 50] [-f]` | The bridge's log |
140
141
  | `bridge map <project> [folder]` | Map a project to a folder (`--remove` to drop it); read on the next wake |
141
- | `bridge unpair` | Revoke the key on the server, remove the service, key and config |
142
+ | `bridge unpair` | Revoke the key on the server, remove the service, key and config; on an unpaired machine, revoke and delete a key an unfinished setup left |
143
+
144
+ ### When setup goes wrong
145
+
146
+ Running `tasqmate bridge setup` again always has a way forward. If the agent was unpaired in Tasqmate, setup clears this machine and pairs again. If this machine is still paired and live, it asks before replacing the pairing (`--replace` skips the question). If an earlier setup stopped after you approved the code, it finds the key that setup left and finishes it here with no new code (`--resume`). Not sure what is wrong? `tasqmate bridge doctor` checks each part and prints the one command that fixes it. Moving an agent to another machine works from the other side too: run setup on the new machine, pick the agent on the pair page and choose Replace.
147
+
148
+ One bridge runs one agent. To run a second agent on the same machine (say Hermes beside Claude), give it a profile: `tasqmate bridge --profile hermes setup --harness hermes`. A profile keeps its own config in `~/.config/tasqmate/bridge-hermes/` and its own background service, and every other bridge command takes the same `--profile hermes` (`bridge --profile hermes status`, `doctor`, `logs`, `map`, `unpair`). Without `--profile` the commands act on the default bridge, as before.
142
149
 
143
150
  What a run may do: read and edit files inside the mapped folder, and use its Tasqmate tools. Shell commands, web access, files outside the folder, and `.git/`, `.claude/` and `.codex/` inside it are refused. A wake on a project with no folder runs in an empty scratch folder, so the agent can still answer but cannot touch code. One run at a time, at most `--runs-per-hour` (default 6) in any hour, each stopped after `--timeout` minutes (30) and `--max-turns` (40). A wake is acknowledged only after its run succeeds; a failed or interrupted run is offered again ten minutes later, up to three times.
144
151
 
@@ -151,6 +158,7 @@ What a run may do: read and edit files inside the mapped folder, and use its Tas
151
158
  | `TASQMATE_WORKSPACE` | Default workspace slug |
152
159
  | `TASQMATE_API_URL` | API origin; defaults to `https://tasqmate.pxlabz.com` |
153
160
  | `TASQMATE_CONFIG_DIR` | Where the stored token lives; defaults to `$XDG_CONFIG_HOME/tasqmate` |
161
+ | `TASQMATE_BRIDGE_PROFILE` | The bridge profile, same as `tasqmate bridge --profile <name>` |
154
162
 
155
163
  ## Exit codes
156
164