Courage
Start in Slack. End with something you can inspect.
Our private company assistant brings agent-assisted work to the place colleagues already talk. One example: turning a request into a working development preview.
Private tool · Public field notes
- SLACK“Can I try this change?”
A colleague asks Courage.
- COURAGE + DEV CENTERA stack for the change.
Worktree → services → development data
- BACK TO THE COLLEAGUEOpen it. Try it. Give feedback.
A company-authenticated preview.
“It works” is not the thing you need to review.
A running preview gives colleagues something to check for themselves. Here’s the workflow described in our public Dev Center case study.
Begin where the work is discussed.
Start the request in Slack. Colleagues don’t need to learn an engineering terminal workflow to ask for a preview.
Reuse the engineers’ tool.
Courage drives Dev Center through its CLI on its own machine. It prepares a stack rather than inventing a separate way to start the application.
Check the application, not the claim.
Open the preview after company sign-in. It uses development data. A useful preview is not a production deployment or proof that a change is ready to ship.
One tool underneath. Different ways in.
Dev Center runs locally, headlessly for Courage, and inside Crafting. The app and CLI share state and actions: we don’t maintain a separate stack launcher just for the agent.
See the app and CLI working together →Native appCourage
CLI