triggeros 0.1.0__tar.gz

triggeros-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+   Copyright 2024 TriggerOS
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

triggeros-0.1.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include README.md
+include LICENSE
+include pyproject.toml

triggeros-0.1.0/PKG-INFO

@@ -0,0 +1,191 @@
+Metadata-Version: 2.4
+Name: triggeros
+Version: 0.1.0
+Summary: Behavioral Operating System for AI Agents — observe, learn, improve.
+Author: TriggerOS
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/triggeros/triggeros
+Project-URL: Repository, https://github.com/triggeros/triggeros
+Project-URL: Documentation, https://github.com/triggeros/triggeros#readme
+Project-URL: Issues, https://github.com/triggeros/triggeros/issues
+Keywords: ai,agents,behavior,learning,cursor,claude
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer>=0.9.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: anthropic>=0.18.0
+Requires-Dist: openai>=1.0.0
+Requires-Dist: PyYAML>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
+Dynamic: license-file
+
+# TriggerOS
+
+**Behavioral Operating System for AI Agents** — observe, learn, improve.
+
+Think: Git for code versioning → TriggerOS for behavioral intelligence versioning.
+
+[![CI](https://github.com/triggeros/triggeros/actions/workflows/ci.yml/badge.svg)](https://github.com/triggeros/triggeros/actions/workflows/ci.yml)  
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+---
+
+## Why TriggerOS?
+
+Why would a dev or engineer run TriggerOS instead of Claude or Codex directly?
+
+- **Project memory** — Learns and reuses facts about *your* repo (e.g. “dashboard = CommandCenterLayout.tsx”, “auth lives in lib/auth”). Future runs start with that context instead of re-exploring. Claude/Codex alone start from zero each time.
+- **Cost control** — Routes work by step: cheap model for planning, stronger one for implementation, mid-tier for tests. You see **total cost and tokens per run** (including multi-step). No more “one expensive model for everything” with no breakdown.
+- **Fewer wrong edits** — File pinning (from task + learned facts) and “read once then patch” discipline reduce “it edited the wrong file.” The agent behaves like it knows your repo.
+- **Learning from corrections** — When you fix agent output, TriggerOS can record it and turn it into conventions (e.g. “live dashboard is CommandCenterLayout, not Header”). Same mistake doesn’t keep happening.
+- **Rules and guardrails** — Patterns can inject prompts, switch model, or block a run (e.g. “no prod deploy without review”). Encode team rules that apply to every run.
+- **Audit and debugging** — `triggeros memory show <id>` shows the **tool-call trace**: which tools, which paths, success/fail, duration. Inspect what the agent did instead of a black box.
+- **One interface, multiple models** — One CLI (`triggeros run "task"`) that can use Claude or OpenAI/Codex and route steps automatically. No switching apps or pasting context by hand.
+
+**TL;DR:** TriggerOS is for when you want the agent to **get better at your project over time**, **spend less** (right model per step + visibility), and **follow rules and learn from corrections** — a project-aware, cost-aware, learning-aware layer on top of Claude/Codex.
+
+---
+
+## What it does
+
+- **Observes** agent actions (prompts, tool calls, outcomes)
+- **Detects** recurring patterns (missing tests, expensive model use, repeated failures)
+- **Applies** learned behaviors (inject prompts, suggest cheaper models)
+- **Learns** from your corrections so the agent gets better over time
+
+TriggerOS agents are **tool-enabled**: they can search/read/write files and run terminal commands inside configured workspace roots (with confirmations by default).
+
+On first run, `triggeros init` can ask your coding style: **vibe coder** (more suggestions), **power user** (fewer, higher-confidence nudges), or **mixed**. It can also discover agents (Claude, OpenAI, Codex) and set a default agent and routing strategy. All of this is stored in `~/.triggeros/config.json`.
+
+---
+
+## Quick start
+
+```bash
+# Install (PyPI — no GitHub needed)
+pip install triggeros
+
+# Set API keys (pick the agents you use)
+triggeros keys template --write              # create .env in cwd
+triggeros keys template --write --config-dir  # or in ~/.triggeros/.env
+# Or export ANTHROPIC_API_KEY / OPENAI_API_KEY in your shell
+
+# Initialize (creates ~/.triggeros, optional questionnaire, agent discovery)
+triggeros init
+
+# Run a task (uses default agent from config if --agent omitted)
+triggeros run "your task"
+triggeros run --agent claude "your task"
+```
+
+**Install from source (developers):** `git clone https://github.com/triggeros/triggeros.git && cd triggeros && pip install -e .`
+
+Customize which env vars we check via `config.json`: set `env_var_names` (e.g. `{"claude": "MY_ANTHROPIC_KEY"}`).
+
+## Commands
+
+| Command | Description |
+|--------|-------------|
+| `triggeros init` | Set up config, DB, optional questionnaire, default agent and routing |
+| `triggeros run [--agent NAME] "<task>"` | Run task through TriggerOS; uses default agent if `--agent` omitted |
+| `triggeros patterns list` | List active patterns (name, confidence, applied, success %) |
+| `triggeros patterns show <name>` | Show one pattern: rules, behavior, stats |
+| `triggeros patterns disable <name>` / `enable <name>` | Disable or re-enable a pattern |
+| `triggeros config show` | Print current config (JSON) |
+| `triggeros config set <key> <value>` | Set config key (e.g. confidence_threshold, default_agent) |
+| `triggeros doctor` | Check config dir, DB, and discovered agents (no key values) |
+| `triggeros keys` | Show API key status (present/missing). `keys template --write` to create .env |
+| `triggeros memory list` | List recent agent actions (id, session, input, started_at, success) |
+| `triggeros memory show <id>` | Full details for one action |
+| `triggeros memory export [--path FILE]` | Export actions and patterns to JSON |
+| `triggeros history` | Last 20 actions (alias for memory list) |
+| `triggeros cost [--limit N] [--period 7d] [--backfill]` | Estimated spend from stored actions (optional backfill for missing cost) |
+| `triggeros stats [--backfill] [--backfill-limit N]` | Sessions, actions, patterns applied, total/avg cost (optional backfill) |
+| `triggeros chats` | List recent chat sessions (~/.triggeros/chats/) |
+| `triggeros` (no args) | Interactive session: prompt loop, optional resume last session |
+| `triggeros --version` | Show version |
+| `triggeros skills ...` | List/install/create/export/import Anthropic-style SKILL bundles |
+| `triggeros learning correction <action-id>` | Record a correction so patterns or skills evolve |
+| `triggeros watch` | Start a local HTTP endpoint (`POST /events/run`, `/events/feedback`) for editors |
+
+## Config
+
+- Config dir: `~/.triggeros` (or `TRIGGEROS_CONFIG_DIR`)
+- `config.json`: `confidence_threshold`, `auto_apply_patterns`, `user_profile`, `default_agent`, `agents_enabled`, `routing_strategy`, `use_routing`, `env_var_names` (optional)
+- `config.json` also tracks `preferred_model_profile` (power / balanced / vibe) and `model_profiles`, which map each profile to the agent/model names TriggerOS should prefer when applying patterns or running tasks. Edit these settings if you want to steer toward Codex/Opus, Claude Sonnet/Haiku, or your own favorites.
+- Cost estimation keys:
+  - `model_pricing` (default `{}`): optional overrides/additions for per-model pricing used by `triggeros cost` / `triggeros stats` (USD per 1M input/output tokens). If a model isn't in TriggerOS' built-in snapshot, add it here.
+- Routing keys:
+  - `use_llm_decomposer` (default true): when routing is enabled, use a cheap LLM call to break a prompt into steps (falls back to heuristic if unavailable)
+  - `decomposer_model_profile` (default vibe): which model profile to use for the decomposition call
+- Tooling policy keys:
+  - `auto_apply_edits` (default false): require confirmation before writing files
+  - `allow_shell_commands` (default false): enable `run_command` / `start_process`
+  - `auto_run_commands` (default false): require confirmation before running commands
+  - `allowed_roots` (default []): extra filesystem roots allowed for tools (cwd is always allowed)
+
+## Setup questionnaire
+
+During `triggeros init` (unless you pass `--yes`), we ask:
+
+- What should TriggerOS call you? (display name used in nudges)
+- How do you like to code? (`vibe`, `power`, `mixed`)
+- Want more suggestions and nudges (tests, cost, etc.)?
+- Which model profile should we lean on (`power`, `balanced`, `vibe`)?
+- Whether TriggerOS can auto-apply edits and run commands, and whether it can access your home directory as an extra root.
+
+Changing these answers updates `user_profile` plus `preferred_model_profile`. You can rerun `triggeros init` later to adjust or edit `~/.triggeros/config.json` directly.
+
+## Project structure
+
+```
+triggeros/
+  core/       # TriggerObject, Pattern, AgentAction, Observer, PatternEngine, BehaviorEngine, LearningLoop, Orchestrator
+  patterns/   # Built-in patterns (missing_tests, cost, reliability)
+  storage/   # SQLite backend, migrations, seed
+  adapters/  # Agent adapters (Claude; OpenAI and routing in later phases)
+  cli/       # Typer CLI: init, run, patterns, config, doctor, memory, history, cost, stats
+  utils/     # Config, discovery (agent detection from env)
+```
+
+## Skills and learning
+
+TriggerOS understands Anthropic-style skills out of the box. Built-in SKILLs live under `triggeros/skills/builtin/`, and the `triggeros skills ...` group lets you list them, install community or custom SKILLs, scaffold templates, and export/import metadata plus any learned improvements. Use `triggeros learning correction <action-id>` after overriding an agent run so the learning loop can create or update patterns and reinforce the relevant skill improvements.
+
+## Editor integration
+
+Run `triggeros watch` to start a small HTTP server (default `http://127.0.0.1:18500`). Cursor or VS Code extensions can push prompts, context, and corrections via `POST /events/run` and `POST /events/feedback`; TriggerOS records those actions, triggers pattern detection, and replies with matched suggestions so editors can surface inline nudges while sharing the same SQLite history and skill data. A helper script `scripts/editor_client.py` demonstrates how to send both run events (`--task`) and feedback (`--feedback-action-id`, `--correction type=... message=... skill=...`) so you can prototype an extension without writing HTTP glue yourself.
+
+For a fully tool-enabled run (TriggerOS executes the agent and tool calls), use `POST /run` with `{ "task": "...", "cwd": "...", "allowed_roots": ["..."], "agent": "openai|claude" }`. This endpoint is non-interactive; enable `auto_apply_edits` / `auto_run_commands` in config if you want it to modify files or run commands without confirmation.
+
+## Advanced CLI automation
+
+`triggeros run` now accepts several automation helpers so you can instruct the CLI to scan directories, grab the files that matter, and tag the intent for the orchestrator before the agent runs:
+
+- `--file/-F PATH`: include a specific file’s content in the run context.
+- `--dir/-D DIR`: walk a directory and attach every file under it (up to 24 entries) so the agent sees the code in question.
+- `--scan-root/-s DIR --find NAME`: search the root for files or folders whose name contains `NAME` (e.g. `–scan-root ~/projects --find receptionist-dashboard`) and feed those snippets into the run.
+- `--tag/-T VALUE`: attach short intent tags such as `classic-dashboard`, `showings`, or `style-match` so patterns and skill learning recognize high-level workflows.
+
+The CLI prints a “Collected context files” table after each run so you can see exactly which files were provided to the agent and preview the snippets that informed the behavior. Use these flags to say things like “scan home for the receptionist-dashboard project, focus on the classic dashboard showings section, and apply the same UI practice to the business page,” and TriggerOS will gather the relevant files, describe the intent, and send it all through the planner + coder pipeline you already built.
+
+## Links
+
+- **Repository:** [github.com/triggeros/triggeros](https://github.com/triggeros/triggeros)
+- **Issues:** [github.com/triggeros/triggeros/issues](https://github.com/triggeros/triggeros/issues)
+- **Contributing:** [CONTRIBUTING.md](CONTRIBUTING.md)
+- **Publishing to PyPI:** [PUBLISH.md](PUBLISH.md) (so users can `pip install triggeros` without GitHub)
+
+## License
+
+Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for the full text.

triggeros-0.1.0/README.md

@@ -0,0 +1,160 @@
+# TriggerOS
+
+**Behavioral Operating System for AI Agents** — observe, learn, improve.
+
+Think: Git for code versioning → TriggerOS for behavioral intelligence versioning.
+
+[![CI](https://github.com/triggeros/triggeros/actions/workflows/ci.yml/badge.svg)](https://github.com/triggeros/triggeros/actions/workflows/ci.yml)  
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+---
+
+## Why TriggerOS?
+
+Why would a dev or engineer run TriggerOS instead of Claude or Codex directly?
+
+- **Project memory** — Learns and reuses facts about *your* repo (e.g. “dashboard = CommandCenterLayout.tsx”, “auth lives in lib/auth”). Future runs start with that context instead of re-exploring. Claude/Codex alone start from zero each time.
+- **Cost control** — Routes work by step: cheap model for planning, stronger one for implementation, mid-tier for tests. You see **total cost and tokens per run** (including multi-step). No more “one expensive model for everything” with no breakdown.
+- **Fewer wrong edits** — File pinning (from task + learned facts) and “read once then patch” discipline reduce “it edited the wrong file.” The agent behaves like it knows your repo.
+- **Learning from corrections** — When you fix agent output, TriggerOS can record it and turn it into conventions (e.g. “live dashboard is CommandCenterLayout, not Header”). Same mistake doesn’t keep happening.
+- **Rules and guardrails** — Patterns can inject prompts, switch model, or block a run (e.g. “no prod deploy without review”). Encode team rules that apply to every run.
+- **Audit and debugging** — `triggeros memory show <id>` shows the **tool-call trace**: which tools, which paths, success/fail, duration. Inspect what the agent did instead of a black box.
+- **One interface, multiple models** — One CLI (`triggeros run "task"`) that can use Claude or OpenAI/Codex and route steps automatically. No switching apps or pasting context by hand.
+
+**TL;DR:** TriggerOS is for when you want the agent to **get better at your project over time**, **spend less** (right model per step + visibility), and **follow rules and learn from corrections** — a project-aware, cost-aware, learning-aware layer on top of Claude/Codex.
+
+---
+
+## What it does
+
+- **Observes** agent actions (prompts, tool calls, outcomes)
+- **Detects** recurring patterns (missing tests, expensive model use, repeated failures)
+- **Applies** learned behaviors (inject prompts, suggest cheaper models)
+- **Learns** from your corrections so the agent gets better over time
+
+TriggerOS agents are **tool-enabled**: they can search/read/write files and run terminal commands inside configured workspace roots (with confirmations by default).
+
+On first run, `triggeros init` can ask your coding style: **vibe coder** (more suggestions), **power user** (fewer, higher-confidence nudges), or **mixed**. It can also discover agents (Claude, OpenAI, Codex) and set a default agent and routing strategy. All of this is stored in `~/.triggeros/config.json`.
+
+---
+
+## Quick start
+
+```bash
+# Install (PyPI — no GitHub needed)
+pip install triggeros
+
+# Set API keys (pick the agents you use)
+triggeros keys template --write              # create .env in cwd
+triggeros keys template --write --config-dir  # or in ~/.triggeros/.env
+# Or export ANTHROPIC_API_KEY / OPENAI_API_KEY in your shell
+
+# Initialize (creates ~/.triggeros, optional questionnaire, agent discovery)
+triggeros init
+
+# Run a task (uses default agent from config if --agent omitted)
+triggeros run "your task"
+triggeros run --agent claude "your task"
+```
+
+**Install from source (developers):** `git clone https://github.com/triggeros/triggeros.git && cd triggeros && pip install -e .`
+
+Customize which env vars we check via `config.json`: set `env_var_names` (e.g. `{"claude": "MY_ANTHROPIC_KEY"}`).
+
+## Commands
+
+| Command | Description |
+|--------|-------------|
+| `triggeros init` | Set up config, DB, optional questionnaire, default agent and routing |
+| `triggeros run [--agent NAME] "<task>"` | Run task through TriggerOS; uses default agent if `--agent` omitted |
+| `triggeros patterns list` | List active patterns (name, confidence, applied, success %) |
+| `triggeros patterns show <name>` | Show one pattern: rules, behavior, stats |
+| `triggeros patterns disable <name>` / `enable <name>` | Disable or re-enable a pattern |
+| `triggeros config show` | Print current config (JSON) |
+| `triggeros config set <key> <value>` | Set config key (e.g. confidence_threshold, default_agent) |
+| `triggeros doctor` | Check config dir, DB, and discovered agents (no key values) |
+| `triggeros keys` | Show API key status (present/missing). `keys template --write` to create .env |
+| `triggeros memory list` | List recent agent actions (id, session, input, started_at, success) |
+| `triggeros memory show <id>` | Full details for one action |
+| `triggeros memory export [--path FILE]` | Export actions and patterns to JSON |
+| `triggeros history` | Last 20 actions (alias for memory list) |
+| `triggeros cost [--limit N] [--period 7d] [--backfill]` | Estimated spend from stored actions (optional backfill for missing cost) |
+| `triggeros stats [--backfill] [--backfill-limit N]` | Sessions, actions, patterns applied, total/avg cost (optional backfill) |
+| `triggeros chats` | List recent chat sessions (~/.triggeros/chats/) |
+| `triggeros` (no args) | Interactive session: prompt loop, optional resume last session |
+| `triggeros --version` | Show version |
+| `triggeros skills ...` | List/install/create/export/import Anthropic-style SKILL bundles |
+| `triggeros learning correction <action-id>` | Record a correction so patterns or skills evolve |
+| `triggeros watch` | Start a local HTTP endpoint (`POST /events/run`, `/events/feedback`) for editors |
+
+## Config
+
+- Config dir: `~/.triggeros` (or `TRIGGEROS_CONFIG_DIR`)
+- `config.json`: `confidence_threshold`, `auto_apply_patterns`, `user_profile`, `default_agent`, `agents_enabled`, `routing_strategy`, `use_routing`, `env_var_names` (optional)
+- `config.json` also tracks `preferred_model_profile` (power / balanced / vibe) and `model_profiles`, which map each profile to the agent/model names TriggerOS should prefer when applying patterns or running tasks. Edit these settings if you want to steer toward Codex/Opus, Claude Sonnet/Haiku, or your own favorites.
+- Cost estimation keys:
+  - `model_pricing` (default `{}`): optional overrides/additions for per-model pricing used by `triggeros cost` / `triggeros stats` (USD per 1M input/output tokens). If a model isn't in TriggerOS' built-in snapshot, add it here.
+- Routing keys:
+  - `use_llm_decomposer` (default true): when routing is enabled, use a cheap LLM call to break a prompt into steps (falls back to heuristic if unavailable)
+  - `decomposer_model_profile` (default vibe): which model profile to use for the decomposition call
+- Tooling policy keys:
+  - `auto_apply_edits` (default false): require confirmation before writing files
+  - `allow_shell_commands` (default false): enable `run_command` / `start_process`
+  - `auto_run_commands` (default false): require confirmation before running commands
+  - `allowed_roots` (default []): extra filesystem roots allowed for tools (cwd is always allowed)
+
+## Setup questionnaire
+
+During `triggeros init` (unless you pass `--yes`), we ask:
+
+- What should TriggerOS call you? (display name used in nudges)
+- How do you like to code? (`vibe`, `power`, `mixed`)
+- Want more suggestions and nudges (tests, cost, etc.)?
+- Which model profile should we lean on (`power`, `balanced`, `vibe`)?
+- Whether TriggerOS can auto-apply edits and run commands, and whether it can access your home directory as an extra root.
+
+Changing these answers updates `user_profile` plus `preferred_model_profile`. You can rerun `triggeros init` later to adjust or edit `~/.triggeros/config.json` directly.
+
+## Project structure
+
+```
+triggeros/
+  core/       # TriggerObject, Pattern, AgentAction, Observer, PatternEngine, BehaviorEngine, LearningLoop, Orchestrator
+  patterns/   # Built-in patterns (missing_tests, cost, reliability)
+  storage/   # SQLite backend, migrations, seed
+  adapters/  # Agent adapters (Claude; OpenAI and routing in later phases)
+  cli/       # Typer CLI: init, run, patterns, config, doctor, memory, history, cost, stats
+  utils/     # Config, discovery (agent detection from env)
+```
+
+## Skills and learning
+
+TriggerOS understands Anthropic-style skills out of the box. Built-in SKILLs live under `triggeros/skills/builtin/`, and the `triggeros skills ...` group lets you list them, install community or custom SKILLs, scaffold templates, and export/import metadata plus any learned improvements. Use `triggeros learning correction <action-id>` after overriding an agent run so the learning loop can create or update patterns and reinforce the relevant skill improvements.
+
+## Editor integration
+
+Run `triggeros watch` to start a small HTTP server (default `http://127.0.0.1:18500`). Cursor or VS Code extensions can push prompts, context, and corrections via `POST /events/run` and `POST /events/feedback`; TriggerOS records those actions, triggers pattern detection, and replies with matched suggestions so editors can surface inline nudges while sharing the same SQLite history and skill data. A helper script `scripts/editor_client.py` demonstrates how to send both run events (`--task`) and feedback (`--feedback-action-id`, `--correction type=... message=... skill=...`) so you can prototype an extension without writing HTTP glue yourself.
+
+For a fully tool-enabled run (TriggerOS executes the agent and tool calls), use `POST /run` with `{ "task": "...", "cwd": "...", "allowed_roots": ["..."], "agent": "openai|claude" }`. This endpoint is non-interactive; enable `auto_apply_edits` / `auto_run_commands` in config if you want it to modify files or run commands without confirmation.
+
+## Advanced CLI automation
+
+`triggeros run` now accepts several automation helpers so you can instruct the CLI to scan directories, grab the files that matter, and tag the intent for the orchestrator before the agent runs:
+
+- `--file/-F PATH`: include a specific file’s content in the run context.
+- `--dir/-D DIR`: walk a directory and attach every file under it (up to 24 entries) so the agent sees the code in question.
+- `--scan-root/-s DIR --find NAME`: search the root for files or folders whose name contains `NAME` (e.g. `–scan-root ~/projects --find receptionist-dashboard`) and feed those snippets into the run.
+- `--tag/-T VALUE`: attach short intent tags such as `classic-dashboard`, `showings`, or `style-match` so patterns and skill learning recognize high-level workflows.
+
+The CLI prints a “Collected context files” table after each run so you can see exactly which files were provided to the agent and preview the snippets that informed the behavior. Use these flags to say things like “scan home for the receptionist-dashboard project, focus on the classic dashboard showings section, and apply the same UI practice to the business page,” and TriggerOS will gather the relevant files, describe the intent, and send it all through the planner + coder pipeline you already built.
+
+## Links
+
+- **Repository:** [github.com/triggeros/triggeros](https://github.com/triggeros/triggeros)
+- **Issues:** [github.com/triggeros/triggeros/issues](https://github.com/triggeros/triggeros/issues)
+- **Contributing:** [CONTRIBUTING.md](CONTRIBUTING.md)
+- **Publishing to PyPI:** [PUBLISH.md](PUBLISH.md) (so users can `pip install triggeros` without GitHub)
+
+## License
+
+Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for the full text.

triggeros-0.1.0/pyproject.toml

@@ -0,0 +1,53 @@
+[build-system]
+requires = ["setuptools>=61.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "triggeros"
+version = "0.1.0"
+description = "Behavioral Operating System for AI Agents — observe, learn, improve."
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.10"
+authors = [{ name = "TriggerOS" }]
+keywords = ["ai", "agents", "behavior", "learning", "cursor", "claude"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development",
+]
+dependencies = [
+    "typer>=0.9.0",
+    "rich>=13.0.0",
+    "anthropic>=0.18.0",
+    "openai>=1.0.0",
+    "PyYAML>=6.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/triggeros/triggeros"
+Repository = "https://github.com/triggeros/triggeros"
+Documentation = "https://github.com/triggeros/triggeros#readme"
+Issues = "https://github.com/triggeros/triggeros/issues"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=7.0.0",
+    "pytest-asyncio>=0.21.0",
+]
+
+[project.scripts]
+triggeros = "triggeros.cli.app:app"
+
+[tool.setuptools.packages.find]
+where = ["."]
+include = ["triggeros*"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+pythonpath = ["."]

triggeros-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

triggeros-0.1.0/triggeros/__init__.py

@@ -0,0 +1,5 @@
+"""TriggerOS — Behavioral Operating System for AI Agents."""
+
+from triggeros.version import __version__
+
+__all__ = ["__version__"]

triggeros-0.1.0/triggeros/__main__.py

@@ -0,0 +1,6 @@
+"""CLI entry: python -m triggeros."""
+
+from triggeros.cli.app import app
+
+if __name__ == "__main__":
+    app()

triggeros-0.1.0/triggeros/adapters/__init__.py

@@ -0,0 +1 @@
+"""Adapters: agents, tools, platforms."""

triggeros-0.1.0/triggeros/adapters/agents/__init__.py

@@ -0,0 +1 @@
+"""Agent adapters."""