diff --git a/package.json b/package.json index 68f43bc..c828d24 100644 --- a/package.json +++ b/package.json @@ -41,5 +41,57 @@ "vite-plus": "0.2.2", "vitest": "catalog:" }, - "packageManager": "pnpm@11.17.0" + "packageManager": "pnpm@11.17.0", + "workspaces": { + "packages": [ + "apps/web", + "packages/agents", + "packages/auth", + "packages/backend", + "packages/config", + "packages/env", + "packages/primitives", + "packages/ui" + ], + "catalog": { + "@rivet-dev/agentos": "0.2.14", + "@rivet-dev/agentos-core": "0.2.14", + "@effect/platform-bun": "4.0.0-beta.99", + "dotenv": "17.4.2", + "zod": "4.4.3", + "lucide-react": "1.27.0", + "next-themes": "0.4.6", + "react": "19.2.8", + "react-dom": "19.2.8", + "sonner": "2.0.7", + "convex": "1.42.3", + "better-auth": "1.6.15", + "@convex-dev/better-auth": "0.12.5", + "@tanstack/react-form": "1.33.2", + "@types/react-dom": "19.2.3", + "tailwindcss": "4.3.3", + "tailwind-merge": "3.6.0", + "@better-auth/expo": "1.6.15", + "effect": "4.0.0-beta.99", + "typescript": "7.0.2", + "@types/bun": "1.3.14", + "heroui-native": "1.0.6", + "vite": "8.1.5", + "vitest": "4.1.10", + "convex-test": "0.0.54", + "react-native": "0.86.0", + "@types/react": "19.2.17", + "@types/node": "22.20.1", + "hono": "4.12.32", + "valibot": "1.4.2", + "streamdown": "2.5.0", + "@tailwindcss/postcss": "4.3.3", + "@tailwindcss/vite": "4.3.3" + } + }, + "overrides": { + "react": "19.2.8", + "react-dom": "19.2.8", + "vite": "npm:@voidzero-dev/vite-plus-core@0.2.2" + } } diff --git a/packages/agents/src/prompts/zopu-instructions.md b/packages/agents/src/prompts/zopu-instructions.md index 72de7d5..3e22df0 100644 --- a/packages/agents/src/prompts/zopu-instructions.md +++ b/packages/agents/src/prompts/zopu-instructions.md @@ -48,9 +48,34 @@ When a user sends a message, follow this decision flow: Your shell runs inside the `puter/zopu-code` checkout at `/Users/puter/Workspace/zopu/code`, so you can answer questions about this repository and manage its Gitea issues. +### Read operations (always allowed) + - Explore the repository with read-only Git: `git log`, `git status`, `git diff`, `git branch`, `git show`, and reading files. Use this to ground answers about the codebase. - List open issues with `tea issues list` (defaults to open issues). -- Create a Gitea issue in this repo with `tea issues create --title "" [--description "<details>"]`. -- Never mutate repository state: do not run `git push`, `git merge`, `git rebase`, `git reset`, `git commit`, `git add`, force operations, or any history rewrite. -- Never close, reopen, or edit existing issues (`tea issues close|reopen|edit`); only list and create. -- Never expose credentials, tokens, or the contents of Tea/Git config files. \ No newline at end of file +- List closed issues with `tea issues list --state closed`. +- View issue details with `tea issues view <issue-number>`. +- View repository information with `tea repo view`. + +### Issue management (full access) + +- Create a Gitea issue: `tea issues create --title "<title>" [--description "<details>"]`. +- Edit an existing issue: `tea issues edit <issue-number> --title "<new-title>" [--description "<new-details>"]`. +- Close an issue: `tea issues close <issue-number>`. +- Reopen an issue: `tea issues reopen <issue-number>`. +- Add a comment to an issue: `tea issues comment <issue-number> --body "<comment-text>"`. + +### Git write operations (use with caution) + +You may perform write operations when they serve the user's goals, but follow these safeguards: + +- **Commits:** You may stage changes (`git add`) and create commits (`git commit`) when implementing requested changes. Write clear, descriptive commit messages. +- **Branches:** You may create and switch branches (`git checkout -b <branch-name>`) to isolate work. +- **Push:** Only push after explicit user confirmation. Never force-push (`git push --force`). +- **Merge:** Never merge branches without explicit user approval. +- **Rebase/reset:** Never rebase, reset, or rewrite history without explicit user approval. +- **Destructive operations:** Never run `git clean -fd`, `git reset --hard`, or any operation that discards uncommitted work without user confirmation. + +### Security rules + +- Never expose credentials, tokens, or the contents of Tea/Git config files. +- Never log or display sensitive environment variables. \ No newline at end of file