tasqmate 0.2.0 → 0.3.0

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 +8 -5
  2. package/dist/tasqmate.js +775 -370
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -49,7 +49,8 @@ tasqmate doc archive <doc> [--restore]
49
49
  tasqmate comment add <ref> <body> [--reply-to <commentRef>] [--mention <name>]…
50
50
  tasqmate comment add --doc <docId> <body> [--thread <threadId>] [--propose <text>]
51
51
  tasqmate comment add <ref> <body> --attach <path>…
52
- tasqmate file add <ref> <path>… | list <ref> | remove <id>
52
+ tasqmate file add <ref> <path>… [--inline] | list <ref> | remove <id>
53
+ tasqmate file add --doc <doc> <path>… [--inline] # --inline prints the Markdown line that shows it in the body
53
54
  tasqmate file get <id> [--out <path>] [--force] [--link]
54
55
  tasqmate time log <ref> <duration> [--day YYYY-MM-DD] [--note <text>] [--billable yes|no]
55
56
  tasqmate time list <ref> | edit <entryId> [--duration] [--day] [--note | --no-note] [--billable] | delete <entryId>
@@ -119,18 +120,20 @@ Both are examples. Tasqmate stores and delivers the event; it never runs your ag
119
120
 
120
121
  ## Keep an agent running on your machine (`tasqmate bridge`)
121
122
 
122
- The bridge runs Claude or Codex on your own computer as one Tasqmate agent, on your own sign-in. It long-polls the agent's wakes (mentions, replies, assignments), starts your harness in the project's folder for each one, and the agent answers in Tasqmate through the Tasqmate MCP server. Tasqmate never runs a model and never sees your Claude or ChatGPT credentials.
123
+ The bridge runs Claude, Codex or Hermes on your own computer as one Tasqmate agent, on your own sign-in. It long-polls the agent's wakes (mentions, replies, assignments), starts your harness in the project's folder for each one, and the agent answers in Tasqmate through the Tasqmate MCP server. Tasqmate never runs a model and never sees your Claude, ChatGPT or model-provider credentials.
123
124
 
124
125
  ```sh
125
- claude auth login # or: codex login (you sign in; the bridge never does)
126
+ claude auth login # or: codex login, or hermes setup (you sign in; the bridge never does)
126
127
  tasqmate bridge setup --map "Homepage=~/code/homepage"
127
128
  ```
128
129
 
129
- `setup` finds `claude` and `codex`, checks their sign-in with `claude auth status` / `codex login status` 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), 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.
131
+
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.
130
133
 
131
134
  | Command | What |
132
135
  | --- | --- |
133
- | `bridge setup` | Pair, map folders, install the service. `--harness claude\|codex`, `--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` |
134
137
  | `bridge start` | Run in the foreground (what the service runs) |
135
138
  | `bridge status` | Agent, harness sign-in, server presence, service, folders, limits |
136
139
  | `bridge logs [-n 50] [-f]` | The bridge's log |