PRINCIPLE_01
GitHub remains the source of truth.
Keep tasks, acceptance criteria and human decisions in GitHub. Labstride adds execution and technical progress without replacing your planning surface.
Open source Self-hosted In development
Open workflows.
Your tools.
A self-hosted foundation for development workspaces and workflows. Connect GitHub issues to isolated workspaces, use your existing CI and delivery workflows, and keep progress visible where you work.
Not a product launch. Specification, contract fixtures and early implementation are public; an installable release is not available yet.
LABSTRIDE / SYSTEM DESIGN
01 — CONCEPTUAL FLOWGitHub remains the interface
01
GitHub issuesTasks · human decisions · visible progress
02
Durable coordinatorExecution identity · SQLite · recovery
03
Isolated SSH workspaceIndependent source checkout per issue
04
GitHub ActionsRepository-owned CI & delivery
+ OPTIONAL Agent & extension adapters
Results & technical progress projected to GitHub↗
GitHub-nativeTask & decision surface
Recovery-orientedDurable execution records
Extensible by contractReplaceable integrations
Operator-controlledSelf-hosted foundation
01 / THE APPROACH
Your workflow stays yours.
Labstride connects the pieces.
The project is designed around ownership, continuity and clear boundaries — not another place to manage your work.
PRINCIPLE_02
Work should survive interruptions.
A small local coordinator records execution identity and recovery state, so uncertainty is handled explicitly rather than blindly repeating actions.
PRINCIPLE_03
Bring your existing stack.
Use repository-owned GitHub Actions and configurable mappings. Connectors, actions and optional agents follow versioned extension contracts.
02 / ARCHITECTURE
A small core.
Clear ownership.
Labstride's adopted design is a durable hybrid: GitHub owns the task and human intent; the coordinator owns execution continuity; your repository owns CI and delivery.
Optional agent integrations participate through explicit, versioned contracts. The public core must work without them.
Read architecture decision ADR-006ARCHITECTURE / RESPONSIBILITY MAP ADOPTED DESIGN
GitHubHUMAN & TASK AUTHORITY
Issues, priorities, acceptance criteria, authorized decisions, visible updates
Coordinator + SQLiteEXECUTION AUTHORITY
Operation identity, claims, durable state, retries, recovery history
SSH targetWORKSPACE RESOURCES
Isolated checkouts, workspace state and authorized operations
GitHub ActionsREPOSITORY EXECUTION
Build, test, packaging and approved delivery workflows
Optional extensionsREPLACEABLE ADAPTERS
Coding sessions, actions and integrations under declared permissions
A responsibility model from the specification. Some components have scoped implementation evidence; this is not a claim of an operational end-to-end release.
03 / DEVELOPMENT STATUS
Built in the open.
Not rushed to release.
Labstride has a public specification and tested implementation slices, but the first installable version is still ahead. The roadmap keeps the remaining integration and release work visible.
Explore work packagesSpecification & architecture
DocumentedProduct boundaries, contracts, security principles, work packages and the durable hybrid architecture are documented publicly.
Early implementation & verification
In progressScoped coordinator, persistence, configuration and Linux/SSH workspace work has implementation and test evidence. Integrated product readiness remains incomplete.
First installable public release
Not releasedEnd-to-end GitHub workflows, delivery, cleanup, operations and clean-install evidence remain before a public prerelease.
04 / GOOD TO KNOW
Questions, answered without the hype.
Can I install Labstride today?
Not yet. The repository contains the specification, executable contracts and selected implementation slices. There is currently no installable public release. Follow the work packages for the remaining steps.
Does Labstride require an AI agent?
No. Agents are optional extensions. The public core is intended to support workspace creation, workflow execution and cleanup without a private agent, its credentials or its hooks.
Will it replace my CI/CD pipeline?
No. Build, test and approved delivery are designed to run through your repository-owned GitHub Actions workflows. Labstride coordinates the work; it is not another build system.
How can I contribute?
Start with the contribution guide or browse the open issues. The project uses Apache-2.0 and DCO sign-off; contributors retain their copyright.
OPEN SOURCE / APACHE-2.0
Help shape the foundation before the first release.
Explore the source, review the design decisions, propose improvements or contribute an extension. The project is public, and contributions are welcome.