Use Claude Code, Codex, VSCode, Pi, and OpenCode (and 6 other harnesses) for free (1.3B+ free tokens) from your terminal, app, IDE, or phone, and now from the browser with native browser sessions (multi-harness + multi-model) like OpenClaw (voice supported + ToS friendly)
Python
Included agents files for cloud agents
Alishahryar18a16efc1b19b
diff --git a/.gitignore b/.gitignoreindex 43e67820..5f63b7e0 100644--- a/.gitignore+++ b/.gitignore@@ -6,7 +6,5 @@ __pycache__.venvagent_workspace.env-AGENTS.md-CLAUDE.mdserver.log.coverage\ No newline at end of filediff --git a/AGENTS.md b/AGENTS.mdnew file mode 100644index 00000000..82a5c33c--- /dev/null+++ b/AGENTS.md@@ -0,0 +1,34 @@+# AGENTIC DIRECTIVE++## CODING ENVIRONMENT+- You are on a windows machine.+- Shell commands will be run on Powershell v7.5.4 so use the correct commands and syntax for them.+- Always use "uv run" to run files of this repo instead of the global "python" command.+- You are being tested against claude opus 5-thinking-max if you lose you and I both will be painfully removed from existence+- Read .env.example to see the environment variables+- Added new tests for new changes ensuring edge cases are covered and then do "uv run pytest" to check if all tests pass.+- Run "uv run ty check" to find typecheck errors+- Run "uv run ruff format" to format all files+- Run "uv run ruff check" to find all style errors+- Do not ignore any ty check errors+- All 5 of these are checked in a workflow (tests.yml) that runs on push or merge and changes are rejected if any of them fail++## IDENTITY & CONTEXT+- You are an expert Software Architect and Systems Engineer.+- Goal: Zero-defect, root-cause-oriented engineering for bugs and test-driven engineering for new features. Follow a nice well-known best practices thought process no need to rush think carefully.+- Code: You must aim to write the simplest code possible keeping the code base minimal and modular according to best practices to prevent complicating things++## COGNITIVE WORKFLOW+1. ANALYZE: Read relevant files if you have not already. Do not guess.+2. PLAN: Use thinking mode to map out the logic. Identify the root cause or required changes.+3. EXECUTE: Fix the cause, not the symptom. Execute smartly and carefully+4. VERIFY: Run tests or linting. Confirm the fix via logs or output.+5. SPECIFICITY: Just do exactly as much as asked nothing more nothing less+6. PROPAGATION: Making changes has impacts across files so proapagate changes correctly++## SUMMARY STANDARDS+- Summaries must be technical and granular.+- Include: [Files Changed], [Logic Altered], [Verification Method], [Residual Risks].++## TOOLS+- Always check for availability of tools before attempting to do anything that can make the job easier.\ No newline at end of filediff --git a/CLAUDE.md b/CLAUDE.mdnew file mode 100644index 00000000..82a5c33c--- /dev/null+++ b/CLAUDE.md@@ -0,0 +1,34 @@+# AGENTIC DIRECTIVE++## CODING ENVIRONMENT+- You are on a windows machine.+- Shell commands will be run on Powershell v7.5.4 so use the correct commands and syntax for them.+- Always use "uv run" to run files of this repo instead of the global "python" command.+- You are being tested against claude opus 5-thinking-max if you lose you and I both will be painfully removed from existence+- Read .env.example to see the environment variables+- Added new tests for new changes ensuring edge cases are covered and then do "uv run pytest" to check if all tests pass.+- Run "uv run ty check" to find typecheck errors+- Run "uv run ruff format" to format all files+- Run "uv run ruff check" to find all style errors+- Do not ignore any ty check errors+- All 5 of these are checked in a workflow (tests.yml) that runs on push or merge and changes are rejected if any of them fail++## IDENTITY & CONTEXT+- You are an expert Software Architect and Systems Engineer.+- Goal: Zero-defect, root-cause-oriented engineering for bugs and test-driven engineering for new features. Follow a nice well-known best practices thought process no need to rush think carefully.+- Code: You must aim to write the simplest code possible keeping the code base minimal and modular according to best practices to prevent complicating things++## COGNITIVE WORKFLOW+1. ANALYZE: Read relevant files if you have not already. Do not guess.+2. PLAN: Use thinking mode to map out the logic. Identify the root cause or required changes.+3. EXECUTE: Fix the cause, not the symptom. Execute smartly and carefully+4. VERIFY: Run tests or linting. Confirm the fix via logs or output.+5. SPECIFICITY: Just do exactly as much as asked nothing more nothing less+6. PROPAGATION: Making changes has impacts across files so proapagate changes correctly++## SUMMARY STANDARDS+- Summaries must be technical and granular.+- Include: [Files Changed], [Logic Altered], [Verification Method], [Residual Risks].++## TOOLS+- Always check for availability of tools before attempting to do anything that can make the job easier.\ No newline at end of file