Show the source
Awaken is Apache-2.0. You can read the code, follow a decision, and propose a better one.
Our principles
Make powerful systems understandable.
Agent systems can act for a long time and across many tools. The people responsible for the work should still be able to see what is happening, decide what is allowed, and change course.
Begin with the work and its owner
A useful system starts with a clear job, a person responsible for it, and a result they can accept. The Agent may plan and act, but it does not get to redefine who decides whether the work is done.
Keep control close to the people doing the work
These choices shape both the software and the way we work with teams adopting it.
Keep operations in your boundary
Run the control plane on infrastructure you choose. Keep Session records and credentials inside that operating boundary.
Leave room to change course
Choose providers and execution backends explicitly. Open protocols and readable formats make later changes easier, though never free.
Name what is ready, and what is not
Plain statusWe distinguish what is available now, what is still a preview, and what remains a target. When a limit matters to your decision, we state it near the claim instead of hiding it in a footnote.
Read the current implementation boundariesMake it easy to question and improve
You do not need to agree with us before taking part. Ask about a design, point out a confusing limit, or improve a small piece of the system. The links below are the direct paths into that work.
GitHub Discussions
Ask a question or propose a change where others can examine it.
Good first issues
Start with a bounded change and its acceptance conditions.
Contributing guide
Follow the repository path from a clone to a reviewed change.
Open decisions & RFCs
Read the unresolved trade-offs and comment on the decision.