-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support for Visualizing and Downloading Final Results in Multiple Formats #155
Labels
Comments
Awesome man. I'll check this in a bit.
…On Thu, Nov 21, 2024, 3:53 PM Dariel Noel ***@***.***> wrote:
Reopened #155 <#155>.
—
Reply to this email directly, view it on GitHub
<#155 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHOIBYOJVCAYCNTLZYWQNPL2BZB4PAVCNFSM6AAAAABSH4WZOOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGM4DQNBXHA3DENY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mattrob333 It's not finished yet; we're still working on it. It's almost ready. We'll keep you updated. |
Hey @mattrob333 do you any example of this that can serve as inspiration? |
Yeah sure. So I've been using Open WebUI lately and they have a good
artifacts component that will render the HTML in the artifact but there is
no way to download or export it anywhere. Ultimately if Kaiban could make
the final agent have the artifact component that presents the final output
like the pdf below, you will have the best tool on the market IMO. Another
very important part is to make this last step have a default MAX token
output and be ran with a model with the largest context window. This last
step in all the agentic frameworks fail to capture all the intermediate
information by forgetting to set the final output to MAX tokens and give
the instruction in the prompt "DO NOT SUMMARIZE OR SHORTEN. RETAIN ALL
VALUABLE INFORMATION FOR THIS COMPREHENSIVE REPORT" or something like that.
Or better yet:
Executive Summary:
{summary of task and a gestalt of entire team output}
Section #1:
{Agent #1 output final markdown version in professional format}
Section #2
{Agent #2 output final markdown version in professional format}
etc
etc
I made two quick docs with some ideas. attached
Excellent work guys. I can wait to see what you come up with.
…On Fri, Nov 22, 2024 at 8:25 AM Dariel Noel ***@***.***> wrote:
Hey @mattrob333 <https://github.com/mattrob333> do you any example of
this that can serve as inspiration?
—
Reply to this email directly, view it on GitHub
<#155 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHOIBYKJLQ36SZ7QGXJOIPD2B4WDZAVCNFSM6AAAAABSH4WZOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTG43DINJTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ai Assistant instruction to create HTML.pdf Adding the 2 PDFs files with the specs you shared @mattrob333 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, KaibanJS provides a streamlined way to visualize workflows and review task results using the Results Overview section. However, users who need to share or store the final outputs—whether in PDF, HTML, or other formats—lack a built-in option to format and download the results directly from the interface. This creates friction for teams that require polished outputs for presentations, reporting, or archival purposes.
Describe the solution you'd like
Integrate functionality within the Results Overview section to visualize and format the final outputs into user-friendly formats like PDF, HTML, or JSON. Add a "Download" button that allows users to save these formatted results as an artifact. This feature could include:
Customization options: Allow users to configure headers, footers, or metadata for the exported results.
Predefined templates: Offer templates for commonly needed formats like reports or presentations.
Interactive preview: Let users preview the formatted results before downloading.
Special thanks to @mattrob333 to bring this up.
The text was updated successfully, but these errors were encountered: