Bring outside work into the workstream and automate the repeatable parts.
Polystro does not assume your workflow starts inside Polystro. It can import prior CLI session history into the workstream model, and it can attach repeatable project actions to that same workstream so setup and launch steps do not have to stay manual.
Imported History
Session import lets Polystro pull conversation history from supported external CLIs into the workstream sidebar. That gives the current workstream continuity even when earlier work happened outside the desktop shell.
What Import Does and Does Not Do
Brings history into the shell
Imported sessions become part of the workstream’s visible history instead of staying scattered across separate tools.
Helps resume context
You can return to prior threads from the same sidebar and search flows as native sessions.
Does not replace the source tool
Import is about continuity and supervision, not about pretending the original tool never existed.
Best used per workstream
Import makes the most sense when you want a repo-anchored history view around a specific workstream.
Project Actions
Project actions are workstream-scoped commands you want easy access to: setup tasks, launch commands, checks, or other repeatable repo operations. They can also be attached to shortcuts or used as part of worktree-oriented setup flows.
When To Use Them
Use import when the missing piece is historical continuity. Use project actions when the missing piece is operational repeatability.