6 comments

  • geraldsterling 4 hours ago ago

    That's pretty cool. With agent task systems, do you plan on having an audit log? With a 'why did this change?' sort of deal. I guess kind of like a history to be able to track which agents did what.

    • hydra-f 3 hours ago ago

      Yes, any agent can authenticate using its model name. The tool automatically tracks the who, when, and what for all actions.

      For monitoring, it comes with local analytics and high-level statistics across the entire board. It logs exactly how the agent ran the "kb" command and whether any failures occured (including the lefthook, for which it automatically scans and runs upon task transition).

      I've also built in various quality-of-life features, such as the files_to_modify field, which automatically keeps track of the work done by the agent:

      IF the agent edits only the specified files, the process proceeds exactly as instructed.

      ELSE, if the agent deviates, the tool generates a full trace of what was and wasn't edited, and automatically appends any newly modified files directly to the JSON.

  • boundless88 6 hours ago ago

    What coding agents are supported right now?

    • hydra-f 6 hours ago ago

      It's model-agnostic, so anything works. As long as the model is good at instruction following, it won't have issues with using the tool (and the AGENTS.md workflow).

  • honestmaker 8 hours ago ago

    love seeing local first terminal tools. switching to the browser just to drag a ticket breaks the flow completely. gonna pull this and test it out.

    • hydra-f 8 hours ago ago

      Thank you! Looking forward to it!