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 story workspaces
Dybs.it can isolate story work using Git branches and worktrees. When the worktree controls are offered for a story, use them to prepare or reopen that story's separate working directory before development. This keeps simultaneous story changes from sharing one checkout.
Availability is release-dependent. If your installed version does not show Git or worktree controls, use your normal Git tooling; the BMad story lifecycle and project documents continue to work without the in-app Git surface.
Never remove a worktree that contains uncommitted work. Dybs.it uses conservative cleanup rules, but you should still commit or intentionally discard changes before closing a story workspace.
After a story merges cleanly from inside Dybs.it, you may be offered a one click
cleanup of that story's workspace. It is always a choice, the branch is kept in
every case, and only the folder is removed. If the folder holds files Git ignores
(a .env, a dist directory, a local cache), Dybs.it names them and asks a
second time, because Git cannot restore those. That second question is always
asked, even if you have told Dybs.it to stop asking the first one.
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.