Documents & History
Dybs.it keeps the plans, story specifications, and AI work around a project easy to find. The available controls depend on the app release and on what exists in the project.
Documents
Open Documents to browse the BMad artifacts Dybs.it discovered in the current project. Typical documents include a product brief, PRD, architecture, epics-and-stories plan, story specifications, and test artifacts.
Select a document to read it. When editing is available, save from the document editor. Dybs.it creates a version before replacing an existing file, allowing you to review earlier saves and restore one if needed.
Important: The files in your project remain the source of truth. Restoring a version changes that project file, so review the result before continuing an agent workflow.
If an expected document does not appear, first confirm that the relevant BMad workflow has created it. You can also use the document picker where offered to point Dybs.it to a non-standard location.
Session history
History records AI sessions associated with the project. Use it to understand which provider and workflow ran, and to return to a previous session when that provider supports resuming.
Resume support is provider-specific. Claude Code sessions can be resumed by session identifier. Providers without compatible resume support start a new session instead; the previous history entry is still retained for reference.
Git and your branches
Dybs.it leaves Git to you. When you start a story, the agent runs in the project folder you have open, on whichever branch is checked out there. Dybs.it does not switch branches, create per-story worktrees, commit, merge or clean anything up on your behalf. Use your normal Git tooling (the command line, your editor, or a Git client) for branches, commits and merges.
Because every story runs in the same checkout, stories you run at the same time share that folder. If you want two stories isolated from each other, create a separate checkout or worktree yourself and open it in Dybs.it as its own project.
If an earlier version of Dybs.it created story worktrees for you, they are left exactly as they were: their folders, branches and any unfinished work stay on disk until you remove them with Git. If a story made progress inside one of those worktrees, its card shows the phase from the project folder you have open (that is the phase Play runs) plus a small Worktree note naming the phase it last reached in the worktree. The note clears once your repository catches up.
Settings
Open Settings to choose an AI provider, configure provider-specific options, change the theme, and run environment diagnostics. Provider choices can include a default plus workflow-specific overrides, depending on the installed provider.