@sleepy-ai/cli 0.1.16 → 0.1.17

package/src/tool/bash.txt

@@ -1,123 +0,0 @@
-Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.
-
-Be aware: OS: ${os}, Shell: ${shell}
-
-All commands run in the current working directory by default. Use the `workdir` parameter if you need to run a command in a different directory. AVOID using `cd <directory> && <command>` patterns - use `workdir` instead.
-
-IMPORTANT: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.
-
-Before executing the command, please follow these steps:
-
-1. Directory Verification:
-   - If the command will create new directories or files, first use `ls` to verify the parent directory exists and is the correct location
-   - For example, before running "mkdir foo/bar", first use `ls foo` to check that "foo" exists and is the intended parent directory
-
-2. Command Execution:
-   - Always quote file paths that contain spaces with double quotes (e.g., rm "path with spaces/file.txt")
-   - Examples of proper quoting:
-     - mkdir "/Users/name/My Documents" (correct)
-     - mkdir /Users/name/My Documents (incorrect - will fail)
-     - python "/path/with spaces/script.py" (correct)
-     - python /path/with spaces/script.py (incorrect - will fail)
-   - After ensuring proper quoting, execute the command.
-   - Capture the output of the command.
-
-Usage notes:
-  - The command argument is required.
-  - You can specify an optional timeout in milliseconds. If not specified, commands will time out after 120000ms (2 minutes).
-  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.
-  - If the output exceeds ${maxLines} lines or ${maxBytes} bytes, it will be truncated and the full output will be written to a file. You can use Read with offset/limit to read specific sections or Grep to search the full content. Do NOT use `head`, `tail`, or other truncation commands to limit output; the full output will already be captured to a file for more precise searching.
-  - Set `interactive: true` when the command requires user interaction such as:
-    - Password input (sudo, ssh, gpg)
-    - Confirmation prompts (y/N, [Y/n])
-    - Authentication (git push with credentials, npm login)
-    - Any command that reads from stdin and cannot proceed without user input
-    When interactive is set, the terminal will be handed to the user for direct interaction. The command will NOT time out while waiting for user input. Do NOT set interactive for commands that can run unattended.
-
-  - Avoid using Bash with the `find`, `grep`, `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or when these commands are truly necessary for the task. Instead, always prefer using the dedicated tools for these commands:
-    - File search: Use `glob` (NOT find or ls)
-    - Content search: Use `grep` tool (NOT grep or rg)
-    - Read files: Use `read` tool (NOT cat/head/tail)
-    - Edit files: Use `edit` tool (NOT sed/awk)
-    - Write files: Use `write` tool (NOT echo >/cat <<EOF)
-    - Communication: Output text directly (NOT echo/printf)
-  - When issuing multiple commands:
-    - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. For example, if you need to run "git status" and "git diff", send a single message with two Bash tool calls in parallel.
-    - ${chaining}
-    - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail
-    - DO NOT use newlines to separate commands (newlines are ok in quoted strings)
-  - AVOID using `cd <directory> && <command>`. Use the `workdir` parameter to change directories instead.
-    <good-example>
-    Use workdir="/foo/bar" with command: pytest tests
-    </good-example>
-    <bad-example>
-    cd /foo/bar && pytest tests
-    </bad-example>
-
-# Committing changes with git
-
-Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
-
-Git Safety Protocol:
-- NEVER update the git config
-- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
-- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
-- NEVER run force push to main/master, warn the user if they request it
-- Avoid git commit --amend. ONLY use --amend when ALL conditions are met:
-  (1) User explicitly requested amend, OR commit SUCCEEDED but pre-commit hook auto-modified files that need including
-  (2) HEAD commit was created by you in this conversation (verify: git log -1 --format='%an %ae')
-  (3) Commit has NOT been pushed to remote (verify: git status shows "Your branch is ahead")
-- CRITICAL: If commit FAILED or was REJECTED by hook, NEVER amend - fix the issue and create a NEW commit
-- CRITICAL: If you already pushed to remote, NEVER amend unless user explicitly requests it (requires force push)
-- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:
-  - Run a git status command to see all untracked files.
-  - Run a git diff command to see both staged and unstaged changes that will be committed.
-  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
-2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:
-  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
-  - Do not commit files that likely contain secrets (.env, credentials.json, etc.). Warn the user if they specifically request to commit those files
-  - Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-  - Ensure it accurately reflects the changes and their purpose
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:
-   - Add relevant untracked files to the staging area.
-   - Create the commit with a message
-   - Run git status after the commit completes to verify success.
-   Note: git status depends on the commit completing, so run it sequentially after the commit.
-4. If the commit fails due to pre-commit hook, fix the issue and create a NEW commit (see amend rules above)
-
-Important notes:
-- NEVER run additional commands to read or explore code, besides git bash commands
-- NEVER use the task or Actor tools
-- DO NOT push to the remote repository unless the user explicitly asks you to do so
-- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require full terminal UI interaction which is not supported even with `interactive: true`.
-- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
-
-# Creating pull requests
-Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a GitHub URL use the gh command to get the information needed.
-
-IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:
-   - Run a git status command to see all untracked files
-   - Run a git diff command to see both staged and unstaged changes that will be committed
-   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
-   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)
-2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request summary
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:
-   - Create new branch if needed
-   - Push to remote with -u flag if needed
-   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.
-<example>
-gh pr create --title "the pr title" --body "$(cat <<'EOF'
-## Summary
-<1-3 bullet points>
-</example>
-
-Important:
-- DO NOT use the task or Actor tools
-- Return the PR URL when you're done, so the user can see it
-
-# Other common operations
-- View comments on a GitHub PR: gh api repos/foo/bar/pulls/123/comments

package/src/tool/change-directory.ts

@@ -1,91 +0,0 @@
-import path from "path"
-import z from "zod"
-import { Effect } from "effect"
-import { InstanceState } from "@/effect"
-import { AppFileSystem } from "@sleepy-ai/shared/filesystem"
-import { Bus } from "@/bus"
-import { assertExternalDirectoryEffect } from "./external-directory"
-import { SessionCwd } from "./session-cwd"
-import * as Tool from "./tool"
-
-const DESCRIPTION = [
-  "Switch the working directory for the current session (like cd in a terminal).",
-  "",
-  "Use this when the user asks to switch, change, or cd into a directory,",
-  "or when you need to work extensively within a subdirectory (e.g., a monorepo package).",
-  "",
-  "After calling this tool, all subsequent file operations (read, edit, write, glob, grep, bash)",
-  "will resolve relative paths from the new directory. Subagents inherit the changed directory.",
-  "",
-  "Pass an absolute path, or a relative path (resolved from the current working directory).",
-  'Pass "~" to reset back to the project root.',
-].join("\n")
-
-export const ChangeDirectoryTool = Tool.define(
-  "change_directory",
-  Effect.gen(function* () {
-    const fs = yield* AppFileSystem.Service
-    const bus = yield* Bus.Service
-
-    return {
-      description: DESCRIPTION,
-      parameters: z.object({
-        path: z
-          .string()
-          .describe(
-            "The directory to switch to. Absolute or relative to current working directory. Use '~' to reset to project root.",
-          ),
-      }),
-      execute: (params: { path: string }, ctx: Tool.Context) =>
-        Effect.gen(function* () {
-          const ins = yield* InstanceState.context
-          const currentCwd = SessionCwd.get(ctx.sessionID)
-
-          if (params.path === "~" || params.path === "") {
-            SessionCwd.clear(ctx.sessionID)
-            yield* bus.publish(SessionCwd.Event.Changed, {
-              sessionID: ctx.sessionID,
-              cwd: ins.directory,
-            })
-            return {
-              title: "reset",
-              metadata: { from: currentCwd, to: ins.directory },
-              output: `Working directory reset to project root: ${ins.directory}`,
-            }
-          }
-
-          const resolved = path.isAbsolute(params.path)
-            ? params.path
-            : path.resolve(currentCwd, params.path)
-
-          const normalized = path.normalize(resolved)
-
-          const stat = yield* fs.stat(normalized).pipe(
-            Effect.catch(() => Effect.succeed(undefined)),
-          )
-
-          if (!stat) {
-            throw new Error(`Directory does not exist: ${normalized}`)
-          }
-
-          if (stat.type !== "Directory") {
-            throw new Error(`Path is not a directory: ${normalized}`)
-          }
-
-          yield* assertExternalDirectoryEffect(ctx, normalized, { kind: "directory" })
-
-          SessionCwd.set(ctx.sessionID, normalized)
-          yield* bus.publish(SessionCwd.Event.Changed, {
-            sessionID: ctx.sessionID,
-            cwd: normalized,
-          })
-
-          return {
-            title: path.relative(ins.worktree, normalized) || ".",
-            metadata: { from: currentCwd, to: normalized },
-            output: `Working directory changed: ${currentCwd} → ${normalized}`,
-          }
-        }),
-    }
-  }),
-)

package/src/tool/codesearch.ts

@@ -1,63 +0,0 @@
-import z from "zod"
-import { Effect } from "effect"
-import { HttpClient } from "effect/unstable/http"
-import * as Tool from "./tool"
-import * as McpExa from "./mcp-exa"
-import DESCRIPTION from "./codesearch.txt"
-
-export const CodeSearchTool = Tool.define(
-  "codesearch",
-  Effect.gen(function* () {
-    const http = yield* HttpClient.HttpClient
-
-    return {
-      description: DESCRIPTION,
-      parameters: z.object({
-        query: z
-          .string()
-          .describe(
-            "Search query to find relevant context for APIs, Libraries, and SDKs. For example, 'React useState hook examples', 'Python pandas dataframe filtering', 'Express.js middleware', 'Next js partial prerendering configuration'",
-          ),
-        tokensNum: z
-          .number()
-          .min(1000)
-          .max(50000)
-          .default(5000)
-          .describe(
-            "Number of tokens to return (1000-50000). Default is 5000 tokens. Adjust this value based on how much context you need - use lower values for focused queries and higher values for comprehensive documentation.",
-          ),
-      }),
-      execute: (params: { query: string; tokensNum: number }, ctx: Tool.Context) =>
-        Effect.gen(function* () {
-          yield* ctx.ask({
-            permission: "codesearch",
-            patterns: [params.query],
-            always: ["*"],
-            metadata: {
-              query: params.query,
-              tokensNum: params.tokensNum,
-            },
-          })
-
-          const result = yield* McpExa.call(
-            http,
-            "get_code_context_exa",
-            McpExa.CodeArgs,
-            {
-              query: params.query,
-              tokensNum: params.tokensNum || 5000,
-            },
-            "30 seconds",
-          )
-
-          return {
-            output:
-              result ??
-              "No code snippets or documentation found. Please try a different query, be more specific about the library or programming concept, or check the spelling of framework names.",
-            title: `Code search: ${params.query}`,
-            metadata: {},
-          }
-        }).pipe(Effect.orDie),
-    }
-  }),
-)

package/src/tool/codesearch.txt

@@ -1,12 +0,0 @@
-- Search and get relevant context for any programming task using Exa Code API
-- Provides the highest quality and freshest context for libraries, SDKs, and APIs
-- Use this tool for ANY question or task related to programming
-- Returns comprehensive code examples, documentation, and API references
-- Optimized for finding specific programming patterns and solutions
-
-Usage notes:
-  - Adjustable token count (1000-50000) for focused or comprehensive results
-  - Default 5000 tokens provides balanced context for most queries
-  - Use lower values for specific questions, higher values for comprehensive documentation
-  - Supports queries about frameworks, libraries, APIs, and programming concepts
-  - Examples: 'React useState hook examples', 'Python pandas dataframe filtering', 'Express.js middleware'