Agent Auto-Tracking

Until now, you had to remind your agent which Frostbyte project it was working in at the start of every session. Add a small .frostbyte.json file to the repo, commit it, and new Claude Code or Codex sessions start with the right project.

The link file holds only the project ID. On session start, a hook reads that ID and tells the agent which project to use. The authenticated read still happens through the MCP server you already connected, so the hook never touches your API token or sends code anywhere.

Your agent keeps the task list current

Once the agent knows the project, it can update the task list while it works. It starts the task you asked for, suggests a new one when the work is big enough to track, adds subtasks to work in progress and marks finished tasks done with a short note on what changed.

New tasks go into the best-fitting existing area when there is one. Releases are left alone unless you ask. Creating a project, linking a repo, opening a task or creating an area still needs your explicit yes.

Onboarding, and a few MCP fixes

In a repo that isn't linked yet, the new onboarding skill offers to sort it out at a natural point. For a fresh codebase, it can create a Frostbyte project and seed the first tasks. For an existing one, it can match the repo to one of your projects and write the .frostbyte.json file.

We also corrected the plugin's area and release tool references so the agent calls MCP tools that exist, and added Auto-tracking docs with the Claude Code and Codex setup paths.