---
title: "Devcontainer support and sessions"
date: "2026-03-02"
---

## Devcontainer support

Sandbox environments can now be defined using standard `devcontainer.json` files. Fabro parses and resolves the full devcontainer spec — features, lifecycle hooks (`onCreateCommand`, `postStartCommand`), build args, `containerEnv`, feature dependencies, and Compose-based configurations.

If your project already has a `.devcontainer/devcontainer.json`, Fabro can use it directly instead of requiring a separate sandbox configuration.

## Sessions

Persistent chat sessions with SQLite storage. Start a conversation with an agent, close the terminal, and pick up where you left off. Sessions track messages, model, and conversation state.

## More

<Accordion title="API">
- New `POST /runs/{id}/preview` endpoint generates a live preview URL for any running sandbox
</Accordion>

<Accordion title="CLI">
- Introduced interactive CLI chat sessions via the now-removed `fabro llm chat` command
</Accordion>

<Accordion title="Improvements">
- GitHub OAuth login for the web app with automatic session management and JWT-based API authorization
- Full documentation site with getting started guides, core concepts, workflow reference, and API docs
- Asset snapshots capture files produced by workflow nodes for review
- Styled 404 and 500 error pages matching the Fabro design system
- `--debug` flag switches log level from INFO to DEBUG for troubleshooting
</Accordion>

<Warning>
**"Pipeline" renamed to "Workflow" and "Run" across the entire system.** API endpoints, CLI commands, config files, and the web UI now use `workflow` and `run` instead of `pipeline`.

To migrate:
1. Replace `pipeline` with `workflow` in DOT files and TOML configs
2. Update API integrations to use new endpoint paths (e.g., `/runs` instead of `/pipelines`)
3. Regenerate API clients with `bun run generate`
</Warning>