Claude Code: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
[https://claude.ai/settings/usage Usage] - [https://platform.claude.com/settings/members Members] | [https://claude.ai/settings/usage Usage] - [https://platform.claude.com/settings/members Members] | ||
== FULL POWER MODE == | |||
You can use the --dangerously-skip-permissions flag when launching Claude Code: | |||
bashclaude --dangerously-skip-permissions | |||
This bypasses all permission prompts so Claude Code will automatically execute commands, write files, etc. without asking. | |||
You can also set it in your project's .claude/settings.json or global settings to configure allowed tools more granularly if you want a middle ground. For example, allowing specific tools like Bash and file editing without prompts while keeping others gated. | |||
== Session Context Preservation == | == Session Context Preservation == | ||
Revision as of 00:02, 2 March 2026
FULL POWER MODE
You can use the --dangerously-skip-permissions flag when launching Claude Code:
bashclaude --dangerously-skip-permissions
This bypasses all permission prompts so Claude Code will automatically execute commands, write files, etc. without asking.
You can also set it in your project's .claude/settings.json or global settings to configure allowed tools more granularly if you want a middle ground. For example, allowing specific tools like Bash and file editing without prompts while keeping others gated.
Session Context Preservation
Prompt:
when using claude code sessions, how do i preserve the context across sessions, even if they run at the same time
When using Claude Code, you can preserve and share context across sessions using a few methods:
CLAUDE.md files
The primary way to persist context is through CLAUDE.md files. Claude Code automatically reads these at the start of each session:
- Project-level: Create a CLAUDE.md in your project root for project-specific context, conventions, and instructions
- User-level: Create ~/.claude/CLAUDE.md for personal preferences that apply across all projects
Session memory with --resume and --continue
claude --continue or -c: Resumes your most recent conversation claude --resume: Opens a session picker to choose from past conversations claude --resume "session-id": Resumes a specific session by ID
For parallel sessions sharing context
If you need multiple simultaneous sessions to share state:
- Use a shared CLAUDE.md file that all sessions read
- Write intermediate results or shared state to files in your project that other sessions can read
- Use claude --print mode for non-interactive sessions that can output to files other sessions consume
Session checkpoints
You can create a checkpoint of your current session's context by asking Claude Code to summarize the current state, and write it to CLAUDE.md or another file.
For the most current and detailed information, check [docs.claude.com the Claude Code documentation], as features may have been added since my knowledge cutoff.
Installation
Install via bash script from here:
curl -fsSL https://claude.ai/install.sh | bash
Plan
WHATEVER YOU CHOOSE, immmediately turn this off, or it will suck up and train on your code:
Settings > Privacy >
There's more crazy privacy stuff to watch out for here.
Billing
- I started with the API usage billing.
- It's expensive. I chewed up $5 pretty fast, so I added $25 more.
- It chewed up $14 of the $30 building sceneKitScrap. Not terrible value, not great either.
- I switched to the Pro plan for $20/month.
- TBD if that will be useful or so limited it is a total waste of time. Max 5x plan is $100/mo. Fucking profiteers.
