# AI use cases for Centra Gideon Agent (Sidiora-Labs/centra-gideon-agent)

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Use cases: 5 | Page: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/

Gideon is a self-hosted personal AI agent platform with a gateway, web console, chat, goal loops, memory, a knowledge base, and a permission-gated app platform.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Run a private personal AI agent from a source checkout: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/self-host-personal-agent-from-checkout/
- Have an agent work a goal across many turns on a schedule: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/run-goal-loop-unattended-on-schedule/
- Run Gideon in one Docker container with persistent state: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/deploy-single-container-gideon-with-docker/
- Build a custom Gideon app with the gideon.sdk package: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/build-custom-gideon-app-with-sdk/
- Make a runtime change and pass the repo's checks: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/contribute-runtime-change-with-repo-checks/

## How to run a private personal AI agent from a source checkout with Centra Gideon Agent

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Build the console, start the gateway, and chat with a self-hosted agent on your own machine.

**Who it is for:** A developer or technical user who wants a personal AI agent that keeps its state on their own machine and works with their chosen model provider.

**The problem:** Hosted assistants keep your conversations and files on someone else's service, and you cannot control which model or local files they use.

**The outcome:** A running gateway and console on your machine, with a separate development state directory and a first chat session.

### Steps

1. Run `python3 -m venv .venv` and then `.venv/bin/python -m pip install -e .` in the checkout.
2. Run `npm ci` and then `npm run build` to build the console.
3. Run `export GIDEON_HOME="$PWD/.dev-home"` and then `.venv/bin/gideon setup`, entering a workspace directory and timezone.
4. Run `.venv/bin/gideon gateway --no-open --port 10000` and open the console address the gateway prints.
5. In the console, configure a model provider or a local model, then start a chat session.

### Prompt to paste into your agent

```text
Work in the Sidiora-Labs/centra-gideon-agent checkout and set up a self-hosted instance using the README self-host steps with GIDEON_HOME set to <state-directory>. Report the console address the gateway prints and the result of the gideon setup prompts. Verify that the gateway answers HTTP requests on port 10000 before reporting success.
```

### Caveat

The README says a fresh home has no provider app yet, so model providers must be added in the console after gideon setup, before any model-backed work runs.

Risk, credentials: The gateway token and the account Gideon runs under grant real access to local files and tools, so store model provider credentials carefully.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/self-host-personal-agent-from-checkout/

## How to have an agent work a goal across many turns on a schedule with Centra Gideon Agent

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Set up a long-running goal loop that works unattended and reports to your inbox.

**Who it is for:** A person with a recurring or multi-step research or admin goal who does not want to supervise each step of the work.

**The problem:** A single chat reply cannot keep working on a goal over many turns, and remembering to restart the work each day is easy to forget.

**The outcome:** A loop that works the goal across turns on a schedule, with results collected in the inbox and the console showing running loops and scheduled jobs.

### Steps

1. Complete the self-host steps through `.venv/bin/gideon gateway --no-open --port 10000` and open the console.
2. In the console, add a model provider so the loop has a model to call.
3. Create a goal loop in the console with a clear goal and a schedule.
4. Check the console for running loops and scheduled jobs after the first scheduled run.
5. Review items that need you in the inbox, and approve tool use when the console asks.

### Prompt to paste into your agent

```text
In the Sidiora-Labs/centra-gideon-agent console, create a goal loop for <goal> on <schedule> and report the loop name, its schedule, and its first status. Verify that the loop appears under running loops and scheduled jobs before you report it as set up.
```

### Caveat

The README lists loops, schedules and tool approvals but does not describe the exact console steps for creating a loop, so confirm the current console screens before you rely on the steps.

Risk, credentials: An unattended loop calls your configured model provider and tools on a schedule, so the provider key and any connected service can be used without you watching each run.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/run-goal-loop-unattended-on-schedule/

## How to run Gideon in one Docker container with persistent state with Centra Gideon Agent

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Build the single-container image from the checkout and run it with a persistent volume.

**Who it is for:** An operator or a Windows user who wants a self-hosted Gideon without installing Python and Node on the host.

**The problem:** Installing Python, Node and the console build on each machine is slow and fragile, and state can be lost when a container is recreated.

**The outcome:** A Gideon container listening on localhost port 10000 that keeps workspace and state on a named volume, with the access URL in the logs.

### Steps

1. Run `docker build -f deploy/docker/Dockerfile.backend --target single -t gideon:local .` from the checkout.
2. Run `docker run -d --name gideon --restart unless-stopped -p 127.0.0.1:10000:10000 -v gideon_home:/data gideon:local`.
3. Run `docker logs gideon` and copy the access URL it prints.
4. Open the access URL in a browser and add a model provider in the console.

### Prompt to paste into your agent

```text
In the Sidiora-Labs/centra-gideon-agent checkout, build the image with the README Docker command and run the container named gideon. Report the access URL from docker logs gideon. Verify that the container is running with docker ps before you report success.
```

### Caveat

The README publishes the port on 127.0.0.1 only, so the console is reachable from the Docker host unless you change that bind address yourself.

Risk, credentials: The container holds your workspace, state and provider credentials on the gideon_home volume, so protect the Docker host and the access URL.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/deploy-single-container-gideon-with-docker/

## How to build a custom Gideon app with the gideon.sdk package with Centra Gideon Agent

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README

Start from the app template in examples and write an app against the Python SDK.

**Who it is for:** A Python developer who wants Gideon to use a model, channel, search, tool or dashboard that the core does not provide.

**The problem:** Integrations added to the core package would make the core harder to maintain, and a new capability needs a clean extension point.

**The outcome:** An app that uses gideon.sdk and keeps its integration outside the core package, ready for the app platform.

### Steps

1. Complete the development setup with `.venv/bin/python -m pip install -e '.[test]'`.
2. Copy the app template from the examples directory into a new folder outside the core runtime. (inferred, check the README)
3. Import the SDK as `gideon.sdk` and implement the model, channel, search, tool or dashboard surface your app needs.
4. Run `make test` to confirm the existing suite still passes after you add the app.
5. Review the permission settings the app requests before you enable it in the platform.

### Prompt to paste into your agent

```text
In the Sidiora-Labs/centra-gideon-agent repository, read the app template under examples and write a new app that uses gideon.sdk to provide <capability>. Report the files you created and the app's requested permissions. Verify that the existing test suite passes with make test before you report success.
```

### Caveat

The README says the examples directory is neither served nor installed, so you must wire your app into the platform yourself rather than expect it to load automatically.

Risk, credentials: An app can call external services with credentials you give it, so limit its permissions to what it needs.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/build-custom-gideon-app-with-sdk/

## How to make a runtime change and pass the repo's checks with Centra Gideon Agent

Repo: [Sidiora-Labs/centra-gideon-agent](https://github.com/Sidiora-Labs/centra-gideon-agent) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Set up the git hooks, make a Python change, and run the format, lint and test targets.

**Who it is for:** A contributor who wants to fix a bug or add a feature in the Gideon runtime and get it through the project's checks.

**The problem:** Changes that skip formatting, sign-off or the test suite get rejected by CI, which wastes review time.

**The outcome:** A runtime change that passes the local format, lint and test targets and carries a DCO sign-off ready for review.

### Steps

1. Run `.venv/bin/python -m pip install -e '.[test]'` and then `sh tooling/scripts/install_git_hooks.sh`.
2. Make your change under runtime/gideon and add or update tests under checks/runtime.
3. Run `make format` and then `make lint`.
4. Run `make test` and fix any failures.
5. Read CONTRIBUTING.md and commit with the DCO sign-off before opening a pull request.

### Prompt to paste into your agent

```text
In the Sidiora-Labs/centra-gideon-agent repository, make the change described as <change> under runtime/gideon, then run make format, make lint and make test. Report the changed files and the final test result. Verify that make lint and make test both finish with no errors before you report the change as ready.
```

### Caveat

The README says the hook script signs commits off and that npm install does not install hooks, so run the hook script separately before you commit.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/sidiora-labs-centra-gideon-agent/contribute-runtime-change-with-repo-checks/