npm - handsoff - Versions diffs - 0.0.1-beta.2 → 0.1.0 - Mend

handsoff 0.0.1-beta.2 → 0.1.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 (8) hide show

package/LICENSE +201 -0
package/README.md +176 -87
package/config.example.toml +15 -0
package/dist/cli/index.js +611 -66
package/dist/cli/index.js.map +1 -1
package/dist/gateway/process.js +11783 -0
package/dist/gateway/process.js.map +1 -0
package/package.json +2 -2

package/LICENSE ADDED Viewed

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+   1. Definitions.
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+   END OF TERMS AND CONDITIONS
+   APPENDIX: How to apply the Apache License to your work.
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+   Copyright [yyyy] [name of copyright owner]
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+       http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md CHANGED Viewed

@@ -1,5 +1,10 @@
 # Handsoff
+[![npm version](https://img.shields.io/npm/v/handsoff)](https://www.npmjs.com/package/handsoff)
+[![npm beta](https://img.shields.io/npm/v/handsoff/beta)](https://www.npmjs.com/package/handsoff?activeTab=versions)
+[![License](https://img.shields.io/npm/l/handsoff)](./LICENSE)
+[![Node.js](https://img.shields.io/node/v/handsoff)](https://nodejs.org/)
 > **Hands off your desk, hand off control to your phone.**
 >
 > *Leave your desk, not your code.*
@@ -24,114 +29,140 @@ No more tethering yourself to your desk. Your code doesn't stop when you step aw
 ---
-## How it works
+## Install (recommended)
-### Claude Code + Telegram integration
+Install globally via npm or pnpm:
-The core workflow bridges Claude Code with Telegram:
+```bash
+npm install -g handsoff
+```
-1. **Session Monitoring** — Handsoff listens for Claude Code session start/end events and notifies you on Telegram
-2. **Permission Control** — When Claude requests to execute a tool, you receive a permission prompt on Telegram with **Allow/Deny** buttons
-3. **Real-time Decisions** — Click the button in Telegram to grant or deny the tool execution
-4. **Task Completion** — Receive final notifications when tasks complete, including execution duration, token usage, and results
+Or run without installing:
-<p align="center">
-  <img src="assets/image_01.jpg" width="45%" alt="Claude + Telegram workflow" />
-  &nbsp;&nbsp;
-  <img src="assets/image_02.jpg" width="45%" alt="Permission request and task completion on Telegram" />
-</p>
+```bash
+npx handsoff init
+```
 ---
-## Architecture
+## Quick start (TL;DR)
-```
-+-------------------------+
-|       CLI Layer         |
-| init | attach | gateway |
-+-----------+-------------+
-            |
-            v
-+-------------------------+
-|   Agent Adapter Layer   |
-| ClaudeHookAdapter       |
-+-----------+-------------+
-            |
-            v
-+-------------------------+
-|     Gateway Layer       |
-| SessionManager          |
-| EventBus | Publisher    |
-| PermissionService       |
-+-----------+-------------+
-            |
-            v
-+-------------------------+
-|   Channel Adapter Layer |
-| Telegram | Feishu       |
-+-------------------------+
+```bash
+# 1. Configure (interactive wizard)
+handsoff init
+# 2. Start the gateway daemon
+handsoff gateway start
+# 3. Start using Codex from your bound chat channel
+# Example: send "/codex explain the latest failing test"
 ```
-- **CLI Layer**: User commands (init, attach, gateway, logs, status)
-- **Agent Adapter Layer**: Translates agent events to unified format
-- **Gateway Layer**: Core hub managing sessions, events, permissions
-- **Channel Adapter Layer**: Sends notifications to messaging platforms
+Done. Codex requests, permission prompts, and task completions will now arrive on your connected channels.
 ---
-## Supported platforms
+## How it works
-- CLI agent support: `claude`
-- Chat channel support: `Telegram`, `Feishu`
+### Claude Code + Telegram integration
----
+The core workflow bridges Claude Code with Telegram:
-## Future plan
+1. **Session Monitoring** — Handsoff listens for Claude Code session start/end events and notifies you on Telegram
+2. **Permission Control** — When Claude requests to execute a tool, you receive a permission prompt on Telegram with **Allow/Deny** buttons
+3. **Real-time Decisions** — Click the button in Telegram to grant or deny the tool execution
+4. **Task Completion** — Receive final notifications when tasks complete, including execution duration, token usage, and results
-- [ ] Add more agent adapters
-- [ ] Add more channel adapters
+<p align="center">
+  <img src="assets/image_01.jpg" width="45%" alt="Claude + Telegram workflow" />
+  &nbsp;&nbsp;
+  <img src="assets/image_02.jpg" width="45%" alt="Permission request and task completion on Telegram" />
+</p>
 ---
-## Installation
-```bash
-npm install -g handsoff
-```
+## How it works
-Or run without installing:
+### Data flow
-```bash
-npx handsoff init
+```
+┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
+│  Claude Code    │     │   Telegram /    │     │   Web / Mobile  │
+│  (agent)        │     │   Feishu        │     │   (-dashboard)  │
+└────────┬────────┘     └────────▲────────┘     └────────▲────────┘
+         │                       │                       │
+         │ hooks                 │ push                  │ ws / http
+         │                       │                       │
+         v                       │                       │
+┌─────────────────┐              │                       │
+│  ClaudeHook     │              │                       │
+│  Adapter        │              │                       │
+└────────┬────────┘              │                       │
+         │                       │                       │
+         │ event                 │                       │
+         │                       │                       │
+         v                       │                       │
+┌─────────────────┐     ┌────────┴───────────────────────┴────────┐
+│   Handsoff      │     │              Gateway                    │
+│   Gateway       │     │  ┌─────────┐  ┌─────────────────────┐  │
+│                 │     │  │EventBus │  │ InteractionService  │  │
+│  ┌───────────┐  │     │  │Session  │  │ NotificationHandler │  │
+│  │ HTTP/WS   │  │◄────┼──│Manager  │  │ EventPublisher      │  │
+│  │  Server   │  │     │  └────┬────┘  └──────────┬──────────┘  │
+│  └───────────┘  │     │       │                   │             │
+└─────────────────┘     └───────┼───────────────────┼─────────────┘
+                                │                   │
+                                │ subscribe         │ publish
+                                │                   │
+                                v                   v
+                       ┌─────────────────┐ ┌─────────────────┐
+                       │ ChannelManager  │ │   Dashboard /   │
+                       │  (Telegram/     │ │     Logger      │
+                       │   Feishu)       │ └─────────────────┘
+                       └─────────────────┘
 ```
----
+1. **Agent hooks** — Claude Code fires lifecycle hooks (`SessionStart`, `PermissionRequest`, `Stop`, etc.)
+2. **Gateway ingests** — `ClaudeHookAdapter` normalizes events and feeds them into the Gateway
+3. **Gateway routes** — `EventBus` routes events to the right handler:
+   - Session events → `NotificationHandler` → push to channels
+   - Permission requests → `InteractionService` → wait for user response
+   - Commands from channels → `Command Handler` → control the agent
+4. **Channels notify** — `ChannelManager` forwards messages to Telegram / Feishu with interactive buttons
+5. **Web dashboard** — HTTP + WebSocket server exposes live sessions and event history
-## Quick start
+### Request/response cycle
-1. Initialize configuration:
+A typical permission-request flow looks like this:
-```bash
-handsoff init
 ```
-2. Start the gateway daemon:
-```bash
-handsoff gateway start
+Claude needs to run Bash
+        │
+        ▼
+Gateway receives PermissionRequest
+        │
+        ▼
+NotificationHandler sends card to Telegram/Feishu
+        │
+        ▼
+User clicks Allow / Deny on phone
+        │
+        ▼
+ChannelManager posts interaction response
+        │
+        ▼
+InteractionService resolves the pending request
+        │
+        ▼
+Claude continues with the result
 ```
-3. Attach an agent:
-```bash
-handsoff attach claude
-```
+---
-4. Check gateway status:
+## Supported platforms
-```bash
-handsoff gateway status
-```
+- CLI agent support: `claude`, `codex`
+- Chat channel support: `Telegram`, `Feishu`, `App`
 ---
@@ -154,8 +185,9 @@ handsoff gateway status
 Most configuration is handled by `handsoff init` interactive wizard, which guides you through:
 1. Setting up your Claude Code hook server port
-2. Configuring Telegram bot credentials
-3. Testing channel connectivity
+2. Enabling Codex agent integration
+3. Configuring Telegram bot credentials
+4. Testing channel connectivity
 For manual setup or advanced options, edit `~/.handsoff/config.toml`. Key sections:
@@ -167,13 +199,29 @@ For manual setup or advanced options, edit `~/.handsoff/config.toml`. Key sectio
 **Telegram channel:**
 - `bot_token` — your Telegram bot token from BotFather
 - `allowed_users` — list of Telegram user IDs allowed to interact with the bot (e.g., `[123456789, 987654321]`)
-- `notify_types` — which event types to forward (`permission_request`, `finished`, `session_start`, `error`, etc.)
+- `notify_types` — which event types to forward (`permission_request`, `question_request`, `finished`, `session_start`, `error`)
+**App channel:**
+- `enabled` — whether to start the App channel WebSocket server with the gateway
+- `channel_id` — unique identifier for this app client (e.g., `app:desktop-001`)
+- `auth_token` — token used to authenticate app clients
+- `heartbeat_interval_ms` — optional heartbeat interval in milliseconds (default: `30000`)
+- `notify_types` — which event types to forward (`*`, `permission_request`, `question_request`, `finished`, `session_start`, `error`)
+Connect to: `ws://localhost:<port>/ws/channels/app`
 **Claude agent:**
 - `adapter` — integration method (always `hooks`)
 - `binary` — Claude Code binary name
 - `permission_mode` — how to handle tool permissions
+**Codex agent:**
+- `enabled` — whether to start the Codex adapter with the gateway
+- `command` — command used to launch `codex app-server`
+- `work_dir` — default working directory for chat-triggered Codex sessions
+- `model` — default Codex model for new sessions
+- `approval_policy` — default approval policy passed to Codex
 Example `~/.handsoff/config.toml`:
 ```toml
@@ -186,7 +234,14 @@ hook_server_port = 9876
 enabled = true
 bot_token = "YOUR_BOT_TOKEN"
 allowed_users = ["123456789"]
-notify_types = ["permission_request", "finished", "session_start", "error"]
+notify_types = ["permission_request", "question_request", "finished", "session_start", "error"]
+[channels.app]
+enabled = false
+channel_id = "app:desktop-001"
+auth_token = "change-me"
+notify_types = ["*"]
+heartbeat_interval_ms = 30000
 [agent.claude]
 adapter = "hooks"
@@ -194,24 +249,58 @@ binary = "claude"
 work_dir = ""
 model = ""
 permission_mode = ""
+[agent.codex]
+enabled = true
+command = ["codex", "app-server", "--listen", "stdio://"]
+work_dir = ""
+model = ""
+approval_policy = ""
 ```
+### Using Codex from Telegram / Feishu
+After the gateway is running and the channel is bound to `codex`, send one of these commands in chat:
+- `/codex <prompt>` — run a Codex task in the current chat
+- `/codex status` — inspect the active Codex session for the current chat
+- `/codex stop` — stop the active Codex session
+- `/codex help` — show the Codex command help
 ---
-## Development
+## From source (development)
+Requires Node.js >= 20.
 ```bash
-npm install
-npm run dev -- init
-npm test
-npm run build
+# Clone the repo
+git clone https://github.com/tapclaw/handsoff.git
+cd handsoff
+# Install dependencies
+pnpm install
+# Development mode
+pnpm run dev -- init
+# Run tests
+pnpm test
+# Build for production
+pnpm run build
 ```
 ---
+## Future plan
+- [ ] Add more agent adapters
+- [ ] Add more channel adapters
+---
 ## Notes
 - Use `config.example.toml` as the starting point.
 - Runtime files are stored in `~/.handsoff`.
-MIT

package/config.example.toml CHANGED Viewed

@@ -27,3 +27,18 @@ permission_mode = ""
 [agent.claude.permission]
 # Low-risk tools that won't trigger permission prompts
 lowRiskTools = ["Read", "Glob", "Grep", "List", "WebSearch", "codesearch"]
+[channels.app]
+enabled = false
+channel_id = "app:desktop-001"
+auth_token = "change-me"
+notify_types = ["*"]
+heartbeat_interval_ms = 30000
+[agent.codex]
+enabled = false
+command = ["codex", "app-server", "--listen", "stdio://"]
+work_dir = ""
+model = ""
+approval_policy = ""
+sandbox_mode = ""