Explain what this repository is about

[fernando-plank]

What this repo about

Agent Context

[ "The repository `fernando-plank/open-swe` is about Open SWE, an open-source cloud-based asynchronous coding agent built with LangGraph. It autonomously understands codebases, plans solutions, and executes code changes across entire repositories—from initial planning to opening pull requests. It features planning, human-in-the-loop interaction, parallel execution, and end-to-end task management, and can be used via a web UI or GitHub issues.", "The `packages/shared` directory contains a common utilities package. It provides shared types, constants, and utilities, exporting modules via the `@open-swe/shared` namespace. It must be built before other packages can import from it and includes crypto utilities, GraphState types, and open-swe specific modules." ]

[fernando-testing-entelligence]

🟠 Plan Ready for Approval 🟠

I've generated a plan for this issue and it's ready for your review.

Plan: Explain what this repository is about

• Task 1:

The repository is about Open SWE, an open-source cloud-based asynchronous coding agent built with LangGraph. It autonomously understands codebases, plans solutions, and executes code changes across entire repositories—from initial planning to opening pull requests. It features planning, human-in-the-loop interaction, parallel execution, and end-to-end task management, and can be used via a web UI or GitHub issues.

Please review the plan and let me know if you'd like me to proceed, make changes, or if you have any feedback.

🟠 Plan Ready for Approval 🟠

I've generated a plan for this issue and it's ready for your review.

Plan: Explain what the fernando-plank/open-swe repository and its shared package are about

• Task 1:

The repository `fernando-plank/open-swe` is about Open SWE, an open-source cloud-based asynchronous coding agent built with LangGraph. It autonomously understands codebases, plans solutions, and executes code changes across entire repositories—from initial planning to opening pull requests. It features planning, human-in-the-loop interaction, parallel execution, and end-to-end task management, and can be used via a web UI or GitHub issues.

• Task 2:

The `packages/shared` directory contains a common utilities package. It provides shared types, constants, and utilities, exporting modules via the `@open-swe/shared` namespace. It must be built before other packages can import from it and includes crypto utilities, GraphState types, and open-swe specific modules.

Please review the plan and let me know if you'd like me to proceed, make changes, or if you have any feedback.

[fernando-plank]

im asking about the fernando-plank/open-swe

[fernando-plank]

and what about the shared packages?