cue-ai 0.4.0 → 0.5.0

package/resources/claude-plugins-official/external_plugins/greptile/README.md

@@ -1,57 +0,0 @@
-# Greptile
-
-[Greptile](https://greptile.com) is an AI code review agent for GitHub and GitLab that automatically reviews pull requests. This plugin connects Claude Code to your Greptile account, letting you view and resolve Greptile's review comments directly from your terminal.
-
-## Setup
-
-### 1. Create a Greptile Account
-
-Sign up at [greptile.com](https://greptile.com) and connect your GitHub or GitLab repositories.
-
-### 2. Get Your API Key
-
-1. Go to [API Settings](https://app.greptile.com/settings/api)
-2. Generate a new API key
-3. Copy the key
-
-### 3. Set Environment Variable
-
-Add to your shell profile (`.bashrc`, `.zshrc`, etc.):
-
-```bash
-export GREPTILE_API_KEY="your-api-key-here"
-```
-
-Then reload your shell or run `source ~/.zshrc`.
-
-## Available Tools
-
-### Pull Request Tools
-- `list_pull_requests` - List PRs with optional filtering by repo, branch, author, or state
-- `get_merge_request` - Get detailed PR info including review analysis
-- `list_merge_request_comments` - Get all comments on a PR with filtering options
-
-### Code Review Tools
-- `list_code_reviews` - List code reviews with optional filtering
-- `get_code_review` - Get detailed code review information
-- `trigger_code_review` - Start a new Greptile review on a PR
-
-### Comment Search
-- `search_greptile_comments` - Search across all Greptile review comments
-
-### Custom Context Tools
-- `list_custom_context` - List your organization's coding patterns and rules
-- `get_custom_context` - Get details for a specific pattern
-- `search_custom_context` - Search patterns by content
-- `create_custom_context` - Create a new coding pattern
-
-## Example Usage
-
-Ask Claude Code to:
-- "Show me Greptile's comments on my current PR and help me resolve them"
-- "What issues did Greptile find on PR #123?"
-- "Trigger a Greptile review on this branch"
-
-## Documentation
-
-For more information, visit [greptile.com/docs](https://greptile.com/docs).

package/resources/claude-plugins-official/external_plugins/imessage/.claude-plugin/plugin.json

@@ -1,11 +0,0 @@
-{
-  "name": "imessage",
-  "description": "iMessage channel for Claude Code \u2014 reads chat.db directly, sends via AppleScript. Built-in access control; manage pairing, allowlists, and policy via /imessage:access.",
-  "version": "0.1.0",
-  "keywords": [
-    "imessage",
-    "messaging",
-    "channel",
-    "mcp"
-  ]
-}

package/resources/claude-plugins-official/external_plugins/imessage/.mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "imessage": {
-      "command": "bun",
-      "args": ["run", "--cwd", "${CLAUDE_PLUGIN_ROOT}", "--shell=bun", "--silent", "start"]
-    }
-  }
-}

package/resources/claude-plugins-official/external_plugins/imessage/ACCESS.md

@@ -1,142 +0,0 @@
-# iMessage — Access & Delivery
-
-This channel reads your Messages database (`~/Library/Messages/chat.db`) directly. Every text to this Mac — from any contact, in any chat — reaches the gate. Access control selects which conversations the assistant should see.
-
-Texting yourself always works. **Self-chat bypasses the gate** with no setup: the server learns your own addresses at boot and lets them through unconditionally. For other senders, the default policy is **`allowlist`**: nothing passes until you add the handle with `/imessage:access allow <address>`.
-
-All state lives in `~/.claude/channels/imessage/access.json`. The `/imessage:access` skill commands edit this file; the server re-reads it on every inbound message, so changes take effect without a restart. Set `IMESSAGE_ACCESS_MODE=static` to pin config to what was on disk at boot.
-
-## At a glance
-
-| | |
-| --- | --- |
-| Default policy | `allowlist` |
-| Self-chat | Bypasses the gate; no config needed |
-| Sender ID | Handle address: `+15551234567` or `someone@icloud.com` |
-| Group key | Chat GUID: `iMessage;+;chat…` |
-| Mention quirk | Regex only; iMessage has no structured @mentions |
-| Config file | `~/.claude/channels/imessage/access.json` |
-
-## Self-chat
-
-Open Messages on any device signed into your Apple ID, start a conversation with yourself, and text. It reaches the assistant.
-
-The server identifies your addresses at boot by reading `message.account` and `chat.last_addressed_handle` from `chat.db`. Messages from those addresses skip the gate entirely. To distinguish your input from its own replies — both appear in `chat.db` as from-me — it maintains a 15-second window of recently sent text and matches against it.
-
-## DM policies
-
-`dmPolicy` controls how texts from senders other than you, not on the allowlist, are handled.
-
-| Policy | Behavior |
-| --- | --- |
-| `allowlist` (default) | Drop silently. Safe default for a personal account. |
-| `pairing` | Reply with a pairing code, drop the message. Every contact who texts this Mac will receive one; only use this if very few people have the number. |
-| `disabled` | Drop everything except self-chat, which always bypasses. |
-
-```
-/imessage:access policy pairing
-```
-
-## Handle addresses
-
-iMessage identifies senders by **handle addresses**: either a phone number in `+country` format or the Apple ID email. The form matches what appears at the top of the conversation in Messages.app.
-
-| Contact shown as | Handle address |
-| --- | --- |
-| Phone number | `+15551234567` (keep the `+`, no spaces or dashes) |
-| Email | `someone@icloud.com` |
-
-If the exact form is unclear, check the `chat_messages` tool output or (under `pairing` policy) the pending entry in `access.json`.
-
-```
-/imessage:access allow +15551234567
-/imessage:access allow friend@icloud.com
-/imessage:access remove +15551234567
-```
-
-## Groups
-
-Groups are off by default. Opt each one in individually, keyed on the chat GUID.
-
-Chat GUIDs look like `iMessage;+;chat123456789012345678`. They're not exposed in Messages.app; get them from the `chat_id` field in `chat_messages` tool output or from the server's stderr log when it drops a group message.
-
-```
-/imessage:access group add "iMessage;+;chat123456789012345678"
-```
-
-Quote the GUID; the semicolons are shell metacharacters.
-
-iMessage has **no structured @mentions**. The `@Name` highlight in group chats is presentational styling — nothing in `chat.db` marks it as a mention. With the default `requireMention: true`, the only trigger is a `mentionPatterns` regex match. Set at least one pattern before opting a group in, or no message will ever match.
-
-```
-/imessage:access set mentionPatterns '["^claude\\b", "@assistant"]'
-```
-
-Pass `--no-mention` to process every message in the group, or `--allow addr1,addr2` to restrict which members can trigger it.
-
-```
-/imessage:access group add "iMessage;+;chat123456789012345678" --no-mention
-/imessage:access group add "iMessage;+;chat123456789012345678" --allow +15551234567,friend@icloud.com
-/imessage:access group rm "iMessage;+;chat123456789012345678"
-```
-
-## Delivery
-
-AppleScript can send messages but cannot tapback, edit, or thread-reply; those require private API. Delivery config is correspondingly limited. Set with `/imessage:access set <key> <value>`.
-
-**`textChunkLimit`** sets the split threshold. iMessage has no length cap; chunking is for readability. Defaults to 10000.
-
-**`chunkMode`** chooses the split strategy: `length` cuts exactly at the limit; `newline` prefers paragraph boundaries.
-
-There is no `ackReaction` or `replyToMode` on this channel.
-
-## Skill reference
-
-| Command | Effect |
-| --- | --- |
-| `/imessage:access` | Print current state: policy, allowlist, pending pairings, enabled groups. |
-| `/imessage:access pair a4f91c` | Approve a pending code (relevant only under `pairing` policy). |
-| `/imessage:access deny a4f91c` | Discard a pending code. |
-| `/imessage:access allow +15551234567` | Add a handle. The primary entry point under the default `allowlist` policy. |
-| `/imessage:access remove +15551234567` | Remove from the allowlist. |
-| `/imessage:access policy pairing` | Set `dmPolicy`. Values: `pairing`, `allowlist`, `disabled`. |
-| `/imessage:access group add "iMessage;+;chat…"` | Enable a group. Quote the GUID. Flags: `--no-mention`, `--allow a,b`. |
-| `/imessage:access group rm "iMessage;+;chat…"` | Disable a group. |
-| `/imessage:access set textChunkLimit 5000` | Set a config key: `textChunkLimit`, `chunkMode`, `mentionPatterns`. |
-
-## Config file
-
-`~/.claude/channels/imessage/access.json`. Absent file is equivalent to `allowlist` policy with empty lists: only self-chat passes.
-
-```jsonc
-{
-  // Handling for texts from senders not in allowFrom.
-  // Defaults to allowlist since this reads your personal chat.db.
-  // Self-chat bypasses regardless.
-  "dmPolicy": "allowlist",
-
-  // Handle addresses allowed to reach the assistant.
-  "allowFrom": ["+15551234567", "friend@icloud.com"],
-
-  // Group chats the assistant participates in. Empty object = DM-only.
-  "groups": {
-    "iMessage;+;chat123456789012345678": {
-      // true: respond only on mentionPatterns match.
-      // iMessage has no structured @mentions; regex is the only trigger.
-      "requireMention": true,
-      // Restrict triggers to these senders. Empty = any member (subject to requireMention).
-      "allowFrom": []
-    }
-  },
-
-  // Case-insensitive regexes that count as a mention.
-  // Required for groups with requireMention, since there are no structured mentions.
-  "mentionPatterns": ["^claude\\b", "@assistant"],
-
-  // Split threshold. No length cap; this is about readability.
-  "textChunkLimit": 10000,
-
-  // length = cut at limit. newline = prefer paragraph boundaries.
-  "chunkMode": "newline"
-}
-```

package/resources/claude-plugins-official/external_plugins/imessage/LICENSE

@@ -1,202 +0,0 @@
-
-                                 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 2026 Anthropic, PBC
-
-   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/resources/claude-plugins-official/external_plugins/imessage/README.md

@@ -1,84 +0,0 @@
-# iMessage
-
-Connect iMessage to your Claude Code assistant. Reads `~/Library/Messages/chat.db` directly for history, search, and new-message detection; sends via AppleScript to Messages.app. No external server, no background process to keep alive.
-
-macOS only.
-
-## Quick setup
-> Default: text yourself. Other senders are dropped silently (no auto-reply) until you allowlist them. See [ACCESS.md](./ACCESS.md) for groups and multi-user setups.
-
-**1. Grant Full Disk Access.**
-
-`chat.db` is protected by macOS TCC. The first time the server reads it, macOS pops a prompt asking if your terminal can access Messages — click **Allow**. The prompt names whatever app launched bun (Terminal.app, iTerm, Ghostty, your IDE).
-
-If you click Don't Allow, or the prompt never appears, grant it manually: **System Settings → Privacy & Security → Full Disk Access** → add your terminal. Without this the server exits immediately with `authorization denied`.
-
-**2. Install the plugin.**
-
-These are Claude Code commands — run `claude` to start a session first.
-
-Install the plugin. No env vars required.
-```
-/plugin install imessage@claude-plugins-official
-```
-
-**3. Relaunch with the channel flag.**
-
-The server won't connect without this — exit your session and start a new one:
-
-```sh
-claude --channels plugin:imessage@claude-plugins-official
-```
-
-Check that `/imessage:configure` tab-completes.
-
-**4. Text yourself.**
-
-iMessage yourself from any device. It reaches the assistant immediately — self-chat bypasses access control.
-
-> The first outbound reply triggers an **Automation** permission prompt ("Terminal wants to control Messages"). Click OK.
-
-**5. Decide who else gets in.**
-
-Nobody else's texts reach the assistant until you add their handle:
-
-```
-/imessage:access allow +15551234567
-```
-
-Handles are phone numbers (`+15551234567`) or Apple ID emails (`them@icloud.com`). If you're not sure what you want, ask Claude to review your setup.
-
-## How it works
-
-| | |
-| --- | --- |
-| **Inbound** | Polls `chat.db` once a second for `ROWID > watermark`. Watermark initializes to `MAX(ROWID)` at boot — old messages aren't replayed on restart. |
-| **Outbound** | `osascript` with `tell application "Messages" to send …`. Text and chat GUID pass through argv so there's no escaping footgun. |
-| **History & search** | Direct SQLite queries against `chat.db`. Full history — not just messages since the server started. |
-| **Attachments** | `chat.db` stores absolute filesystem paths. The first inbound image per message is surfaced to the assistant as a local path it can `Read`. Outbound attachments send as separate messages after the text. |
-
-## Environment variables
-
-| Variable | Default | Effect |
-| --- | --- | --- |
-| `IMESSAGE_APPEND_SIGNATURE` | `true` | Appends `\nSent by Claude` to outbound messages. Set to `false` to disable. |
-| `IMESSAGE_ALLOW_SMS` | `false` | Accept inbound SMS/RCS in addition to iMessage. **Off by default because SMS sender IDs are spoofable** — a forged SMS from your own number would otherwise bypass access control. Only enable if you understand the risk. |
-| `IMESSAGE_ACCESS_MODE` | — | Set to `static` to disable runtime pairing and read `access.json` only. |
-| `IMESSAGE_STATE_DIR` | `~/.claude/channels/imessage` | Override where `access.json` and pairing state live. |
-
-## Access control
-
-See **[ACCESS.md](./ACCESS.md)** for DM policies, groups, self-chat, delivery config, skill commands, and the `access.json` schema.
-
-Quick reference: IDs are **handle addresses** (`+15551234567` or `someone@icloud.com`). Default policy is `allowlist` — this reads your personal `chat.db`. Self-chat always bypasses the gate.
-
-## Tools exposed to the assistant
-
-| Tool | Purpose |
-| --- | --- |
-| `reply` | Send to a chat. `chat_id` + `text`, optional `files` (absolute paths). Auto-chunks text; files send as separate messages. |
-| `chat_messages` | Fetch recent history as conversation threads. Each thread is labelled **DM** or **Group** with its participant list, then timestamped messages (oldest-first). Omit `chat_guid` to see every allowlisted chat at once, or pass one to drill in. Default 100 messages per chat. Reads `chat.db` directly — full native history. |
-
-## What you don't get
-
-AppleScript can send messages but not tapback, edit, or thread — those require Apple's private API. If you need them, look at [BlueBubbles](https://bluebubbles.app) (requires disabling SIP).