Repository navigation
Vertical clips with a hook from a long video, in the dashboard's chat - #86
Merged
Merged
Conversation
… the conversation
…in the conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The request we get most: one long edited interview, 5–6 vertical clips with a strong hook. This makes it one sentence in the conversation, and moves the conversation into the Clawnify dashboard's chat when the app runs there.
What changes
Clips from a long video (
make_clips,src/server/clips.ts)Framing the cut (
reframe): the same analysis on the current cut, into its 9:16 version (added if missing).Waiting inside a background job: a task is resumable state inside
InstructState. A step that has to wait on the transcript or the analyses ends the delivery, and the next delivery picks it up. Project ids are chosen before anything is created, so a lost delivery never creates a project twice. The task gives up after 40 minutes and keeps the whole picture for what didn't answer. Both operations always run in the background.Dashboard chat (
@clawnify/app0.2.1 → 0.4.5,@clawnify/db→ ^0.4.3 so there is only one copy)openChat). The editor tells the chat which project is open (useChatContext) and adds four "/" commands.useHostChanges). The chat can also open a clip it made through the app's router (useHostNavigate).agent.mdtells the dashboard chat to send requests to/instruct(withbackground: truefor anything that watches footage) instead of writing the document itself.Smaller changes:
requestFramingandreadFramingare shared by the route and the job, with no change in behaviour. The new schema column isask_messages.made.Tests
test/clips.test.ts(12 tests) covers:madein the background runcoverwith a crop; the asking project is unchanged.vitest: 305 pass.test:e2e: all pass.tscandvite buildare clean.Not tested here: the embedded dashboard-chat path needs the dashboard. It gets checked on Circulate after release.