[Tracking] Assistant work after the move

Open
  • Is something wrong?
#420 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend-api-design

Research direction

Read the linked issues #414, #415, #409, #412, and #410 to understand their scope and dependencies, then check blockers #400 and #398. The tracking issue is done when all five are closed or closed as not wanted, each with a one-line reason.

Written by the indexing model from the issue text.

Description

tech-debt

Groups the assistant (assistant/) work that follows the monorepo move (#397, done: #398 closed 2026-11-06). All of it except #410 waits for #400, because assistant feature work uses the merged pipeline.

Suggested order

  1. #410 — One-command install and update: the plugin and MCP server run from a runtime folder outside the repo, not from the clone (redesigned 2026-11-06; needs grooming; not blocked by #400, and first because it changes how the assistant is run every day)
  2. #414 — Report created tasks when create_tasks hits a transport error (bug; also set_journal_todos). Independent of the others.
  3. #415 — Stop get_journal from silently creating entries and carrying tasks forward (bug; needs a design decision first). Decide with #409 part 3 and #412 item 1, since all three change how moved tasks are reported.
    3a. [ ] #422 — Show planned subtasks in the planned list and count them in the Planned tasks (N) header of get_journal (needs grooming; changes the same tool output as #415, so build them together)
  4. #409 — Planning reliability in task tools (parts 2 to 4; part 3 is decided with #415).
  5. #412 — Review the smaller API gaps (item 1 is decided with #415; items 7 to 9 came from asst#37).

Notes

  • #411 (run the MCP client against the real API in CI) is not here: it is part of the move and is listed in #397.
  • #414, #415, #409, #412 and #422 are blocked by #400 on GitHub. #410 is not (the blocker was removed on 2026-11-06), so it can be done before the pipeline merge.
  • #409, #410 and #412 were transferred from nevridge/taskflow-assistant on 2026-11-04; their old references redirect.

Done when

All six are closed or closed as not wanted, each with a one-line reason.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.