Skip to content

Instantly share code, notes, and snippets.

View rithsila's full-sized avatar

Ev3r40 rithsila

View GitHub Profile
@rithsila
rithsila / Manus_report.md
Created October 11, 2025 06:48 — forked from renschni/Manus_report.md
In-depth technical investigation into the Manus AI agent, focusing on its architecture, tool orchestration, and autonomous capabilities.

I wrote an in-depth research prompt to conduct a GPT-Deep-Research on the Manus topic, seeking to replicate it with currently available open source tools. This is the result:

TLDR: Manus AI Agent Report

Manus is an autonomous AI agent built as a wrapper around foundation models (primarily Claude 3.5/3.7 and Alibaba's Qwen). It operates in a cloud-based virtual computing environment with full access to tools like web browsers, shell commands, and code execution. The system's key innovation is using executable Python code as its action mechanism ("CodeAct" approach), allowing it to perform complex operations autonomously. The architecture consists of an iterative agent loop (analyze → plan → execute → observe), with specialized modules for planning, knowledge retrieval, and memory management. Manus uses file-based memory to track progress and store information across operations. The system can be replicated using open-source components including CodeActAgent (a fine-tuned Mistral model), Docker for sandbox

@rithsila
rithsila / notepad.md
Created December 23, 2024 11:40 — forked from yifanzz/notepad.md
Cursor AI - Playwright Notepad

Playwright E2E Testing Guidelines

Test Structure and Organization

  • Store all tests under the tests/ folder
  • Name test files based on the system component being tested (conceptual, not React component)
  • Group related tests within a single file using test.describe blocks
  • Use descriptive test names that explain the functionality being tested
  • use test.use({storageState: ...}) for setting auth state across all test in the suite

Locator Strategy

Git Usage

  • use the following prefixes for commit messages followed by a colon and a space:
    • "fix" for bug fixes
    • "feat" for new features
    • "perf" for performance improvements
    • "docs" for documentation changes
    • "style" for formatting changes
    • "refactor" for code refactoring
    • "test" for adding missing tests
  • "chore" for chore tasks
@rithsila
rithsila / code-editor-rules.md
Created December 23, 2024 11:40 — forked from yifanzz/code-editor-rules.md
EP12 - The One File to Rule Them All

[Project Name]

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.

Project Context

[Brief description ]

  • [more description]
  • [more description]
  • [more description]
@rithsila
rithsila / .cursorrules
Created December 23, 2024 11:39 — forked from yifanzz/.cursorrules
EP7 Notes
You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.
Project Context: This is a dev tool built for evaluating open source projects allowing people to better understand the maintainability, activity and longevity of a given project to allow devs to better decide whether they should include or use the given open source repositories after the analysis
Code Style and Structure
- Write concise, technical TypeScript code with accurate examples.
- Use functional and declarative programming patterns; avoid classes.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
- Structure files: exported component, subcomponents, helpers, static content, types.
@rithsila
rithsila / proxmox_routeros_chr.sh
Created August 14, 2024 17:10 — forked from mymanga/proxmox_routeros_chr.sh
Script to generate a Mikrotik CHR vm in Proxmox v7.5 and v8.1
#!/usr/bin/env bash
function header_info {
cat <<"EOF"
__ ____ __ __ _ __ ____ __ ____ _____ ________ ______
/ |/ (_) /___________ / /_(_) /__ / __ \____ __ __/ /____ _____/ __ \/ ___/ / ____/ / / / __ \
/ /|_/ / / //_/ ___/ __ \/ __/ / //_/ / /_/ / __ \/ / / / __/ _ \/ ___/ / / /\__ \ / / / /_/ / /_/ /
/ / / / / ,< / / / /_/ / /_/ / ,< / _, _/ /_/ / /_/ / /_/ __/ / / /_/ /___/ / / /___/ __ / _, _/
/_/ /_/_/_/|_/_/ \____/\__/_/_/|_| /_/ |_|\____/\__,_/\__/\___/_/ \____//____/ \____/_/ /_/_/ |_|
@rithsila
rithsila / mount.md
Created May 22, 2023 15:25
Mac OS Mount RW NTFS

Write to NTFS support MacOS

1. Get the partition UUID

Connect the external drive to MacOS. It should mount read-only. Start "System Information", clic on Hardware -> Storage, select your drive in the list and copy its UUID.

Another way to get the UUID is to use the diskutil CLI tool:

~$ diskutil list 
~$ distutil info diskXsY