omnigent
AI coding agent server. Omnigent is a meta-harness for running, governing and collaborating on AI coding agents from a shared server, with native OIDC login, policies and session history.
The OIDC session cookie secret needs to be 64 hex characters, generate it with openssl rand -hex 32.
Example
{
nps.stacks.omnigent = {
enable = true;
db = {
type = "postgres";
passwordFile = config.sops.secrets."omnigent/db_password".path;
};
oidc = {
enable = true;
clientSecretFile = config.sops.secrets."omnigent/oidc/client_secret".path;
cookieSecretFile = config.sops.secrets."omnigent/oidc/cookie_secret".path;
# clientSecretHash = ... # optional, defaults to hashing clientSecretFile
};
};
}Stack Options
nps.stacks.omnigent.db.passwordFile
The file containing the PostgreSQL password for the database. Only used if db.type is set to "postgres".
nps.stacks.omnigent.db.type
Type of the database to use.
Can be set to "sqlite" or "postgres".
If set to "postgres", the passwordFile option must be set.
nps.stacks.omnigent.db.username
The PostgreSQL user to use for the database. Only used if db.type is set to "postgres".
nps.stacks.omnigent.enable
Whether to enable omnigent.
nps.stacks.omnigent.extraEnv
Extra environment variables to set for the container. Variables can be either set directly or sourced from a file (e.g. for secrets).
See https://omnigent.ai/docs/deploy/overview#docker-compose for available variables.
attribute set of (null or boolean or signed integer or string or absolute path or (submodule))
{ }
{
OMNIGENT_FEATURES = "usage_page";
OMNIGENT_SHARING_MODE = "read_only";
}
nps.stacks.omnigent.oidc.clientSecretFile
The file containing the client secret for the OIDC client that will be registered in Authelia.
For examples on how to generate a client secret, see
https://www.authelia.com/integration/openid-connect/frequently-asked-questions/#client-secret
absolute path
config.sops.secrets."immich/authelia/client_secret".path"
nps.stacks.omnigent.oidc.clientSecretHash
The client secret hash. For examples on how to generate a client secret, see https://www.authelia.com/integration/openid-connect/frequently-asked-questions/#client-secret
The value can be passed in multiple ways:
- As a literal string
- As an absolute path to a file containing the hash (
toFile) - As an absolute oath to a file containing the client_secret, in which case the hash will be automatically computed (
toHash) - As
null
If left unset (null), the client secret will be read from the file specified in the clientSecretFile option and hashed automatically before being passed to the Authelia container.
null or string or (submodule)
null
# Literal String:
"$pbkdf2-sha512$310000$cbOAIWbfz3vCVXIPIp6d2A$J0klwULa6TvPRCU1HAfuKua/dMKTl8gbTYJz2N73ejGUu0LUGz/y3kwmJLuKuAYGg3WQOT0q9ZzVHHUvpKpgvQ"
# Client secret hash stored in a file
{ fromFile = config.sops.secrets."immich/client_secret_hash".path; }
# Client secret stored in a file: Hash will be computed dynamically
{ toHash = config.sops.secrets."immich/client_secret".path; }
# Null (default): Hash will be computed automatically based on the clientSecretFile option
# Equivalent to { toHash = cfg.oidc.clientSecretFile; }
null
nps.stacks.omnigent.oidc.cookieSecretFile
File containing the OIDC session cookie secret (64 hex characters).
Generate with openssl rand -hex 32.
nps.stacks.omnigent.oidc.enable
Whether to enable OIDC login with Authelia. This will register an OIDC client in Authelia and setup the necessary configuration.
Omnigent has native OIDC support and handles the login flow itself.
For details, see:
nps.stacks.omnigent.oidc.userGroup
Users of this group will be able to log in
