01
Built with operators
The product should reflect how teams actually work: messy context, approval steps, shared channels, and evolving internal rules.
Community
Build more useful AI, together.
Friday grows through real workflows, clear documentation, and contributions that keep automation legible and under human control.
3Community principles
4Places to participate
OpenOpen project
01 / How we build
Useful, inspectable, shareable.
The community keeps Friday close to real problems and makes each new capability understandable before it becomes automation.
02
Documented by default
Workflows, prompts, provider choices, and integration settings should be easy to inspect, improve, and share.
03
Open to contributors
Add adapters, improve starter workflows, write docs, or help shape the safety model for agentic desktop tools.
02 / Join in
Follow development and contribute where you can help.
Follow development, propose improvements, and share workflows that can help other people too.
Contribute a workflow
Turn your repeated task into a reusable command.
Start with the sample data and replace it with your real contribution paths, docs, and repository links.