Skip to content

[Resource]: Ralph workflow #1523

Description

@rickvian

Display Name

ralph-workflow

Category

Workflows & Knowledge Guides

Sub-Category

Workflows & Knowledge Guides: Ralph Wiggum

Primary Link

https://rickvian.github.io/ralph-workflow/

Author Name

Rickvian aldi

Author Link

https://github.com/rickvian

License

MIT

Other License

No response

Description

Scaffold everything you need to run Ralph safely inside a VS Code Dev Container with isolated GitHub credentials and an autonomous AI coding loop.

https://rickvian.github.io/ralph-workflow/

Validate Claims

Ralph workflow idea:

Ralph runs with --dangerously-skip-permissions (or similar), which means it has full access to whatever credentials are available inside the container.
Pain poin of isolating Ralph:

  • spin up docker container by yourself.
  • what if you want to give ralph minimal access to the repo? you have to set your own github PAT through few manual steps inconvenient web navigations.
  • if you want to leverage vscode container, its by default come with credential forwarding which is dangerous!

ralph-workflow provide convenience for you to scaffolds those things:

  • The Dev Container, that acts as a hard boundary.
  • VS Code credential-forwarding is neutralized by a postStarthook before Ralph runs. VSCode dev container is well integrated with VSCode IDE which makes it convenient to quickly reopens project in container anytime.
  • The only credential Ralph ever sees is a fine-grained PAT you mount from your host — scoped to one repo.

Specific Task(s)

the scaffold script provide isolation to claude to run in ralph loop with --dangerously-skips-permission safely, you can easily spin more project using this, throw in requirement, it will loop and develop feature by itself

Specific Prompt(s)

npx ralph-workflow to setup the isolation environment and ralph scaffold, choose claude or other, setup PAT, credential forwarding clearing, etc

Additional Comments

No response

Recommendation Checklist

  • I have checked that this resource hasn't already been submitted
  • It has been over one week since the first public commit to the repo I am recommending
  • All provided links are working and publicly accessible
  • I do NOT have any other open issues in this repository
  • I am primarily composed of human-y stuff and not electrical circuits

Metadata

Metadata

Assignees

No one assigned

    Labels

    resource-submissionThis Issue submits a new resource to the listvalidation-passedResource has passed initial validation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions