Passing improved context to update and update-tasks for more relevant instructions #36
Pinned
eyaltoledano
started this conversation in
Ideas
Replies: 1 comment
-
|
Would be partly solved with note versioning, or some other kinds of relational diagram #487 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The
updatecommand is super useful if you need to pivot MANY tasks forward of a specific task where things are changingas i go through @ralph_ecom's PR for the MCP server, it occured to me it would be nice to be able to update Task 23 (mcp server) via Perplexity. Only that one task.
So I implemented the
update-taskcommand. It works exactly the same way. You pass it a prompt and --research and goes and resarches what else is missing to get this task working. Very useful for blurry R&D--
Then I ran into the need for the context awareness upgrades I been talking about. I need to be able to pass also what we have implemented so far to this
update-taskcommand so Perplexity can give me accurate and relevant steps based on where we are with the subtasks and implementation uncertaintySo I tried to bootstrap the feature.
To pass full files and code context to the
updateandupdate-taskcommands, here is what I did:update-taskcommand's prompt dynamically by concatenating the prompt with the file contents of the files relevant to our task (in the case of MCP server that's index.js and server.js and package.json)node scripts/dev.js update-task --id=23 --research --prompt="$(cat /tmp/prompt.txt) $(cat /tmp/encoded_files.txt)"💡 This is how we can bootstrap passing context for now until we develop a proper --context flag. But that context flag would effectively be working this way.
Beta Was this translation helpful? Give feedback.
All reactions