- Default model: anthropic/claude-opus-4-5 → anthropic/claude-opus-4-7
- Quota switcher: claude-opus-4-6 → claude-opus-4-7
- Update all provider defaults and test fixtures
- Update comments/docstrings referencing old model names
- Claude Opus 4.7 released 2026-04-16, same pricing as 4.6
Used nonexistent 'system_prompt' variable. Match the keyword-arg call
pattern used at the top of _process_message.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
chat() had a blanket `except Exception` that swallowed LongContextError,
preventing the agent loop from catching it for auto-consolidation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When Anthropic returns 429 "Extra usage is required for long context
requests", the agent now automatically runs memory consolidation and
trims the session, then retries the LLM call with shorter context.
- Add LongContextError exception in providers/base.py
- Provider detects long-context 429 and raises immediately (no retry)
- Agent loop catches it in both _process_message and _process_system_message
- Consolidates facts, trims session, rebuilds messages, retries
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The extraction LLM returns facts as {"fact": "...", "date": "..."} dicts
instead of plain strings. store_facts now normalizes these to strings
before passing to mem0.add(). Also fixes KeyError when slicing dicts
in the error handler.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2000 tokens is insufficient for large sessions (700+ messages), causing
JSON truncation and parse failures.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- test_oauth_identity_block: verify identity block is included in API
requests even when system=None (covers fix in 3f2684d)
- test_mem0_extract_facts: verify extract_facts passes thinking_budget=0
to provider.chat() (covers fix in 76d5a73)
- test_session_audit_log: verify save() creates append-only audit log
with markers and message preservation (covers feat in 2ab6494)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fact extraction inherited the instance thinking_budget (10000), causing
the model to spend tokens on thinking instead of outputting JSON. The
response content was empty, failing JSON parse every time.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Every SessionManager.save() now also appends the full session state
to a parallel audit file (*.audit.YYYY-MM.jsonl). This survives
session trims and memory consolidation — when something wipes the
session, the audit file retains the complete history.
Rotated monthly by filename. Never truncated.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Anthropic requires the identity prefix for OAuth tokens on every
request, but it was only included when a system prompt was present.
Calls without a system prompt (e.g. fact extraction during memory
consolidation) got 400 invalid_request_error every time, silently
breaking memory consolidation while the session trim still ran.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Anthropic now requires OAuth requests to include an approved identity
string as a separate first content block in the system prompt array.
Without it, Sonnet/Opus models return 400 invalid_request_error.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Comprehensive guide for using the staging environment:
- Quick start with test-pr.sh script
- Manual testing methods
- Cache verification procedures
- Session management
- Troubleshooting tips
Includes examples for multi-turn testing and cache validation.
Intermediate assistant messages (with tool_calls) and tool result messages
are never sent to the user but remain in the model's context. This causes
the model to refer to content the user never saw.
Add _hidden_sig field at message creation time (context.py), then apply
[HIDDEN:sig] prefix at read time (session get_history) so the model sees
which messages were hidden. Storing the signature separately from content
preserves Anthropic prompt caching — the same prefixed string is produced
every turn.
Changes:
- visibility.py: add compute_signature(), refactor sign_content/verify to
use it, fix Tuple -> tuple (PEP 585)
- context.py: add_assistant_message() and add_tool_result() store _hidden_sig
- session/manager.py: get_history() applies [HIDDEN:sig] prefix at read time
- tests/test_message_visibility.py: 14 tests covering compute_signature,
_hidden_sig creation, get_history prefix, JSONL round-trip, idempotency
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Intermediate assistant messages (with tool_calls) and tool result messages
are never sent to the user but remain in the model's context. This causes
the model to refer to content the user never saw.
Add _hidden_sig field at message creation time (context.py), then apply
[HIDDEN:sig] prefix at read time (session get_history) so the model sees
which messages were hidden. Storing the signature separately from content
preserves Anthropic prompt caching — the same prefixed string is produced
every turn.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove oauthCredentials dict after extracting api_key to avoid duplication
- Use _ for unused provider_name variable per convention
Addresses review feedback from PR #32.
Use + refspec to force update pr-N branch on re-run. Prevents
'already exists' error when testing the same PR multiple times.
Addresses review feedback from PR #32.
Creates test-pr.sh to streamline PR testing workflow:
- Fetches PR from wylab remote
- Checks out PR branch
- Installs in editable mode with uv
- Runs test with staging config
- Uses NANOBOT_CONFIG to isolate from production
Usage: ./test-pr.sh <pr-number> [test-message]
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Added logic to _migrate_config() to automatically populate the api_key field
from oauthCredentials.access_token when present. This allows configs that
store OAuth tokens in the oauthCredentials structure to work correctly.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Modify get_config_path() to check NANOBOT_CONFIG env var first before
falling back to ~/.nanobot/config.json. This allows staging/custom
setups to use a different config file without modifying code.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Fixes all critical warnings from test suite:
1. **DeprecationWarning: datetime.utcnow()** (anthropic_oauth.py:458)
- Replace `datetime.utcnow()` with `datetime.now(datetime.UTC)`
- Python 3.12+ deprecation, will be removed in future versions
- Affects API header debug logging
2. **RuntimeWarning: unawaited coroutine** (test_agent_loop_tool_result.py:31)
- Change `session_mgr.save = AsyncMock()` to `MagicMock()`
- Mock was async but production code is synchronous
- Affected 4 tests (tool result handling tests)
**Test Results:**
```
======================= 277 passed in 7.61s =======================
```
All RuntimeWarning and DeprecationWarning eliminated from nanobot tests.
Note: PytestCacheWarning persists due to root-owned .pytest_cache directory
(cosmetic only, run with `-p no:cacheprovider` for clean output).
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit fixes 9 test failures by addressing:
1. Computer tool VNC mocking (3 tests)
- Fixed mock path from VNCDoToolClient to vnc_api.connect
- Fixed captureScreen to write file instead of returning bytes
- Fixed key press to expect lowercase keys
2. Onboard command fixture (4 tests)
- Added workspace_dir.mkdir() in test fixture
- Updated exit code expectations to match actual behavior
- Fixed assertion messages
3. System prompt identity test (1 test)
- Removed outdated test - feature moved to agent loop
4. Cron timezone validation (1 test)
- Restored --tz flag (removed in f959185 as collateral damage)
- Restored CLI-level validation
- Restored try/except wrapper for service errors
All 277 tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Add [matrix] optional dependencies section to pyproject.toml
(matrix-nio, mistune, nh3) to match error message guidance
- Fix test mock function signature to accept positional args
instead of keyword-only args (removed *,)
- Fix test assertions to handle optional metadata keys
using .get("attachments", []) instead of ["attachments"]
All 45 matrix channel tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
These tests were for /stop command functionality that was removed
during the quota-based model switching refactor (commit 19a81e1).
Tests were checking for methods that no longer exist:
- _handle_stop()
- _dispatch()
- _active_tasks
- _session_tasks
- cancel_by_session()
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The runtime context (channel/chat_id) is now included in the system
prompt instead of being a separate user message. This is a deliberate
design change to simplify the message structure.
Changes:
- ✅ Updated test to expect runtime context in system prompt
- ✅ Updated test description to reflect new behavior
- ✅ Removed assertions for separate user message
Test now passes with the current implementation.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The AnthropicOAuthProvider always includes hardcoded beta flags:
- claude-code-20250219
- oauth-2025-04-20
- context-management-2025-06-27
Tool-specific beta flags are then merged with these and sorted
alphabetically. Tests were only checking for tool flags, not the
combined result.
Changes:
- ✅ Updated test_oauth_utils.py to expect all hardcoded flags
- ✅ Updated test_beta_flags_collected_from_tools to expect combined flags
- ✅ Updated test_multiple_beta_flags_joined to expect combined flags
All 3 beta flags tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The EditTool20250728 uses the name "str_replace_based_edit_tool" but
tests were checking for the old name "str_replace_editor". This commit
updates all test expectations to use the correct tool name.
Changes:
- ✅ Updated test_edit_tool.py to expect "str_replace_based_edit_tool"
- ✅ Updated test_native_tools_registration.py for correct tool name
- ✅ Updated test_registry_native_execution.py to execute with correct name
- ✅ Removed computer tool assertion (intentionally disabled by default)
All 3 EditTool naming tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The SubagentManager.spawn() method was returning a human-readable status
message, but tests (and wait_for()) expected it to return the task ID
directly. This commit fixes both the implementation and the tests:
Implementation changes:
- spawn() now returns the task_id (string) instead of a status message
- Updated docstring to reflect the correct return value
- Status message is still logged for debugging
Test changes:
- Updated spawn() calls to use new parameter structure:
* Changed from: origin={"channel": "x", "chat_id": "y"}
* Changed to: origin_channel="x", origin_chat_id="y"
This makes spawn() more useful programmatically - callers can use the
returned task_id with wait_for() without parsing a message.
All 3 SubagentManager tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The HeartbeatService constructor was refactored to use an on_heartbeat
callback instead of accepting provider/model parameters directly. This
commit updates the tests to match the new API:
- Removed DummyProvider class (no longer needed)
- Updated test_start_is_idempotent to use new constructor
- Removed test_decide_returns_skip_when_no_tool_call (_decide method no longer exists)
- Updated test_trigger_now_executes_when_decision_is_run to use on_heartbeat callback
- Updated test_trigger_now_returns_none_when_no_callback to test new behavior
Also fixed a bug where start() was not idempotent - it now checks if a
task is already running before creating a new one.
All 3 HeartbeatService tests now pass.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
When the agent uses the message tool to reply to the same channel/chat_id
as the incoming message, the final automatic reply is now suppressed to
prevent duplicate messages to the user.
Changes:
- MessageTool: add _sent_in_turn flag and start_turn() method
- MessageTool.execute(): set flag when sending to same target as context
- AgentLoop._process_message(): call start_turn() at beginning
- AgentLoop._process_message(): return None if message tool already sent
This restores functionality that was accidentally removed during refactoring
(originally implemented in commits fafd8d4, 29e6709).
Fixes 3 failing tests in test_message_tool_suppress.py
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The test_consolidate_offset.py file contained ~100 tests for the
last_consolidated field which no longer exists. Since the field and its
incremental consolidation behavior have been removed, these tests are
obsolete.
Also removed redundant empty check in memory.py consolidation (if
len <= keep_count, then slice will be empty).
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The `last_consolidated` marker was designed for incremental consolidation
assuming append-only messages. However, deferred trim removes messages from
the session, which broke the incremental assumption and caused consolidation
to fail silently (early exit when end_idx <= stale last_consolidated).
After trim, the session only contains NEW unconsolidated messages, making
the marker unnecessary. Consolidation now always starts from index 0,
processing all messages in the session (which are by definition not yet
consolidated due to trim).
Fixes the bug where extraction completely stopped working after trim
(zero facts extracted despite multiple consolidation attempts).
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
System messages (including subagents) can trigger memory_consolidate,
which sets _trim_checkpoint. The system handler must also check and
apply deferred trims to prevent unbounded session growth.
Addresses review feedback from PR #17.
**Problem:**
When memory_consolidate is called mid-turn, deferred trim was using a
relative count (_pending_trim) that gets applied after the turn completes.
This caused the trim to recalculate the cut point based on the FINAL session
size (after messages were added), and _trim_to_clean_boundary would walk
backward to find a user message, often landing at the START of the current
turn and wiping all prior history.
Example: Session with 426 messages, consolidate sets pending_trim=10, turn
grows to 440 messages, trim calculates cut=430, finds no user messages in
430-439 (all tool chain), walks back to position 426 (current turn start),
wipes messages 0-425.
**Solution:**
Replace relative count with absolute checkpoint position:
- At consolidation time: calculate checkpoint = len(session) - keep_count
- Find clean boundary at or before checkpoint (not after turn completes)
- Store absolute position in session._trim_checkpoint
- At trim time: simply slice session.messages[checkpoint:]
This preserves the intended trim point regardless of messages added during
the remainder of the turn.
**Testing:**
Hot-patched and verified:
- Before: consolidation wiped all history, kept only current turn (16 msgs)
- After: consolidation preserved history correctly (23 msgs from before consolidation)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
nanobot
code-server
wylab