Start with the existing behavior
Read the versioned guide, check the installed version and look for an existing issue. A reproducible report should name the command, expected result, actual result and relevant environment.
Remove credentials and personal data from logs before sharing them. Never include passwords, access keys, private keys, tokens or cookies.
Propose a focused change
Use an issue to explain the problem or a pull request to propose a patch. Include the reason for the change and proportionate validation. Keep unrelated edits separate so they can be reviewed.
Clone the project
git clone https://framebridge.betancourt.one/git/gerardo/framebridge.gitOfficial releases and free forks
Maintainers review which changes become official FrameBridge releases. Published release checksums and signatures identify those artifacts.
GNU GPLv3 also allows private modifications and independently distributed forks, subject to its terms. Contributing changes upstream is welcome; it is not a condition for exercising those rights. Modified builds should be clearly marked and must not be presented as official project releases.
Read the GNU GPLv3 license. Third-party components retain their existing notices and licenses.
Using an agent to contribute
The command interface and MCP guide are designed for both people and authorized agents. Normal operation uses installed commands and tools. Editing or rebuilding the application is a development task that should follow the owner’s instructions.
Project credits
Programming: ChatGPT
Original concept and project coordination: Gerardo Betancourt
FrameBridge is an independent project. The credit describes how the project was developed and does not imply endorsement by OpenAI.