Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Simplify Custom Chain Execution with .chain Files (Chain of Thoughts format) #16

Open
PatrickDiallo23 opened this issue Dec 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@PatrickDiallo23
Copy link
Collaborator

PatrickDiallo23 commented Dec 2, 2024

Introduce a feature that processes .chain files to create and manage custom chains of request execution. Each step in the chain corresponds to a specific prompt (or task), and steps are organized into (sub)folders for modular management. Also, those steps can be automatically executed or done with user confirmation (ask before moving to the next step). Changes to steps will trigger rollbacks and re-execution of subsequent steps.

Example Workflow:

  1. Input .chain file:
Implement an application that collects user data and saves it in [[file]].csv.  (01_step)
---  
Cover it with tests.  (02_step)
---  
Add REST endpoint for [[file]].csv.  (03_step)

Note: LLM can be asked to split a bigger task into these steps.
2. System generates:

chain/01_step/01_step_prompt.txt
chain/02_step/02_step_prompt.txt
chain/03_step/03_step_prompt.txt

Note: Optionally, a batch file to execute steps sequentially can be created as well.
3. Execution proceeds step by step (with or without user approval), with rollback if step modifications occur.

A new directive (#chain-confirmations: on/off) can be implemented in .chain files to toggle between fully automated execution and user-confirmed execution. This allows users to customize how the chain steps are processed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant