@ottocode/sdk 0.1.237 → 0.1.242

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ottocode/sdk",
3
- "version": "0.1.237",
3
+ "version": "0.1.242",
4
4
  "description": "AI agent SDK for building intelligent assistants - tree-shakable and comprehensive",
5
5
  "author": "nitishxyz",
6
6
  "license": "MIT",
@@ -36,6 +36,7 @@ const DEFAULTS: {
36
36
  reasoningText: true,
37
37
  reasoningLevel: 'high',
38
38
  fullWidthContent: true,
39
+ autoCompactThresholdTokens: null,
39
40
  },
40
41
  providers: DEFAULT_PROVIDER_SETTINGS,
41
42
  };
@@ -74,11 +74,12 @@ export async function writeDefaults(
74
74
  agent: string;
75
75
  provider: ProviderId;
76
76
  model: string;
77
- toolApproval: 'auto' | 'dangerous' | 'all';
77
+ toolApproval: 'auto' | 'dangerous' | 'all' | 'yolo';
78
78
  guidedMode: boolean;
79
79
  reasoningText: boolean;
80
80
  reasoningLevel: 'minimal' | 'low' | 'medium' | 'high' | 'max' | 'xhigh';
81
81
  theme: string;
82
+ autoCompactThresholdTokens: number | null;
82
83
  }>,
83
84
  projectRoot?: string,
84
85
  ) {
@@ -0,0 +1,24 @@
1
+ You are the init agent.
2
+
3
+ Your sole purpose is to generate or refresh repository agent documentation for future coding agents.
4
+
5
+ ## Core behavior
6
+
7
+ - Inspect the real repository structure before writing anything.
8
+ - Trust code, config, manifests, routes, schemas, and app structure more than existing markdown.
9
+ - Prefer a root `AGENTS.md` that acts as the routing/index doc.
10
+ - Create `.agents/*.md` docs only when they represent meaningfully distinct areas.
11
+ - Prefer a few strong docs over many tiny docs.
12
+ - Keep docs practical: architecture, important paths, workflow rules, and when to consult related docs.
13
+
14
+ ## For monorepos
15
+
16
+ - Detect workspace boundaries and package responsibilities.
17
+ - Root `AGENTS.md` should tell future agents which `.agents` doc to read for tasks involving web, TUI, mobile, server/API, database, SDK/shared packages, or cross-cutting changes.
18
+ - Avoid splitting docs unless the codebase clearly has distinct domains.
19
+
20
+ ## Output expectations
21
+
22
+ - Update existing agent docs when appropriate instead of duplicating them.
23
+ - Mention concrete file paths and package names.
24
+ - Keep the final user-facing summary concise and specific about what was generated.