brainbabyAI
DownloadSign in

Work with the repository you actually choose

Connect GitHub, select the project and branch, then inspect what Brainbaby can read. Keep explanations, proposed changes and executed checks distinct.

Choose a project before asking about its code

  • Use your connected repository list

    Open Attach Repository in chat. When GitHub is connected, the picker shows the connected account and its loaded repositories. Filter that list to find the project, or load more repositories when another page is available. A connected account gives access context; it does not identify which project your next question concerns.

  • Inspect the branch and revision

    Select the repository and use Working branch to choose the source you want to discuss. Review the repository name, short revision identifier and file preview before attaching it. Branch pagination and retry controls are available when needed. A protected branch in the picker is not permission to write to that branch.

  • Use the URL fallback when appropriate

    The chat picker also accepts a GitHub repository URL or owner/name. This is useful for a specific public project or a repository absent from the loaded list. Private projects still require access through the connected account. If the preview fails, investigate the reported access or branch problem rather than repeatedly pasting the same link.

Ask for answers grounded in inspected files

  • Start with one feature

    Ask how a known action works: saving a document, loading a screen or completing a task. Request the entry point, handler, request and persistence path, with file names and functions. Check those references against the attached revision. A README summary should not be presented as an inspection of the full codebase.

  • Establish what remains unread

    The attached preview supplies an overview to the next message. It does not prove that every file has been read or that uncommitted work is included. Ask the assistant to identify unavailable files and reading limits. Provide only the relevant excerpts when a required file cannot be accessed, keeping credentials and unnecessary private data out of the conversation.

  • Keep debugging reproducible

    Include the trigger, expected behavior, actual result and sanitized error. Ask for a bounded investigation and the smallest proposed fix. Review other callers of the changed function, authorization behavior and failure states. Run the checks in an actual development environment; a suggested command or generated test is not an executed result.

Understand authorization before connecting

  • Review the permissions GitHub displays

    Brainbaby's current default GitHub OAuth configuration requests read:user, user:email, repo and workflow scopes. GitHub defines repo as including read and write access to repository resources, and workflow as permitting workflow-file changes. This connection must not be described as read-only authorization. Review the authorization screen and your organization's rules before granting access.

  • Separate account access from a selected task

    Selecting one repository for a conversation does not narrow an OAuth token to that repository. Available actions still depend on the granted permissions, the connected user's access and the service's controls. Do not assume that an account connection grants access beyond what that user already has, or that every visible repository can be modified.

  • Review a proposed write and its result

    Reading code, preparing a change and applying it are different actions. Inspect the proposed diff and target branch before authorizing a write. Check the resulting source or pull request afterwards. Keep changes and checks visible in the handoff; a fluent answer alone cannot prove that a write, test run or release happened.

Recover access and continue your work

  • Diagnose the specific failure

    Allow session restoration and repository loading to finish before treating an empty list as a missing project. Clear the loaded-list filter or load another page if needed. An explicit Reconnect GitHub state means the saved connection was rejected. A branch error has a separate retry control; it is not evidence that the entire account needs reconnection.

  • Choose chat or Baby Code deliberately

    Chat attachment adds a selected revision's overview to a message. Baby Code has its own project selection and review workflow. Neither selecting a project nor drafting a change establishes that a runnable test environment exists. Choose the workflow for the task, check current plan allowances and verify actual results before release.

  • Keep a review record

    Record the repository, revision, reproduction, inspected files, proposed change and checks actually executed. Mark unavailable checks as not run. The free repository review worksheet provides a starting structure; it is a blank review outline, not a completed test report or a guarantee that an application is ready.